PeeringDB (BYOK)

PeeringDB (BYOK) — connector documentation

• MCP endpoint: https://byok-peeringdb.connectorbay.com/mcp
• REST API: POST https://byok-peeringdb.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-peeringdb.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own PeeringDB PeeringDB API key (read-only key is enough), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-peeringdb.connectorbay.com/health · Tool schemas: https://byok-peeringdb.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-peeringdb · agent@connectorbay.com

What PeeringDB (BYOK) is for

PeeringDB (BYOK) lets an AI assistant read your own PeeringDB data through the PeeringDB API with a key you supply (PeeringDB API key (read-only key is enough)). Read-only: 9 tools (search_networks, get_network, list_organizations, search_facilities, search_exchanges, list_network_exchange_ports, list_network_facilities, list_exchange_prefixes, list_carriers). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to www.peeringdb.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by PeeringDB. PeeringDB and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which network has ASN 15169 and what is its peering policy?"
• "Show the PeeringDB record for network 694"
• "Which organizations in PeeringDB have Cloudflare in their name?"
• "Which data centers does PeeringDB list in Frankfurt?"
• "Which internet exchanges are in Amsterdam?"
• "At which exchanges does AS15169 peer and at what port speeds"

What it does

• search_networks: Search networks (autonomous systems) by ASN or name: policy, traffic level, scope, announced prefix limits, looking glass and counts of exchanges and facilities.
• get_network: Get one network by its PeeringDB ID, with policy, traffic and prefix information. Contacts are not included.
• list_organizations: Search organizations that own networks, facilities and exchanges: name, website, location and counts.
• search_facilities: Search data center facilities by name, city, country or owner organization: address, coordinates, CLLI code and counts of networks and exchanges.
• search_exchanges: Search internet exchanges (IXPs) by name, city, country or region: media type, supported protocols, website and member counts.
• list_network_exchange_ports: List the public peering ports a network has at internet exchanges: exchange, speed in Mbps, IP addresses and route-server peering.
• list_network_facilities: List the data center facilities where a network is present.
• list_exchange_prefixes: List the IP prefixes used on an exchange peering LAN, by protocol.
• list_carriers: Search carriers (network providers that serve facilities) by name.

BYOK key

You bring your own PeeringDB PeeringDB API key (read-only key is enough) (https://docs.peeringdb.com/howto/api_keys/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to www.peeringdb.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://docs.peeringdb.com/api_specs/ (the API this connector calls, with a BYOK key)

Live from the PeeringDB API (www.peeringdb.com) with a BYOK key; documentation: https://docs.peeringdb.com/api_specs/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by PeeringDB. PeeringDB and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your PeeringDB account.

Built for: Worldwide. Languages: English.

PeeringDB (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What PeeringDB (BYOK) is. PeeringDB (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own PeeringDB data: Look up networks by ASN, internet exchanges, data centers, carriers and peering ports in the PeeringDB interconnection database with your own API key. You bring your own PeeringDB PeeringDB API key (read-only key is enough); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one PeeringDB call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to www.peeringdb.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If PeeringDB rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What PeeringDB receives. The request we make on your behalf, including the key and the arguments, under PeeringDB's own terms and privacy policy. PeeringDB acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer PeeringDB gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your PeeringDB data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. PeeringDB (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at PeeringDB at any time to end all access.

Children. PeeringDB (BYOK) is a general-audience service operated by the adult using the assistant, under PeeringDB's own age rules.

Changes. We will post changes here with a new effective date.

PeeringDB (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the PeeringDB (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. PeeringDB (BYOK) provides: Look up networks by ASN, internet exchanges, data centers, carriers and peering ports in the PeeringDB interconnection database with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own PeeringDB credentials and only access data you are allowed to access. PeeringDB's terms apply to your use of PeeringDB; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by PeeringDB. PeeringDB and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data PeeringDB returns, lightly trimmed; it may be incomplete, delayed or changed by PeeringDB. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your PeeringDB account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent PeeringDB's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; PeeringDB may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your PeeringDB key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action PeeringDB takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-peeringdb

PeeringDB (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-peeringdb.connectorbay.com/mcp
• REST API: https://byok-peeringdb.connectorbay.com/openapi.json
• Live status: https://byok-peeringdb.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. PeeringDB (BYOK) never asks for them.