BGP.tools API

Name: BGP.tools API API
Brand: BGP.tools API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey6 EndpointsREST

For Agents

Export the global BGP routing table, ASN-to-name mappings, and curated network tags from BGP.tools for IP intelligence and network research.

Quickstart

Get started with BGP.tools API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"look up asn organisation name"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with BGP.tools API API.

Export the full IPv4 and IPv6 BGP routing table as plaintext or JSONL

Look up ASN-to-organisation name mappings across the global routing system

Retrieve the list of curated tags used by BGP.tools to classify networks

Download the members of a specific tag (such as anycast or hosting) as CSV

GET STARTED

Start building with BGP.tools API API

Explore with Jentic

View OpenAPI Document

Use for: I need to download the current global BGP routing table, Get the ASN-to-name mapping for all autonomous systems, List all available BGP.tools tags, Find every prefix tagged as anycast

Not supported: Does not handle IP geolocation, abuse reporting, or whois lookups — use for BGP routing table exports and ASN-to-organisation mappings only.

The BGP.tools API exports BGP routing data sourced from a global view of the Internet routing table. It returns the full IPv4 and IPv6 prefix-to-ASN routing table, ASN-to-organisation mappings, and curated tag lists used to flag networks (for example anycast, hosting, or government). All requests must include a custom User-Agent header that identifies the requester so the operators can contact heavy users. Output is plaintext, CSV, or JSONL — there is no JSON object response.

Use Cases

Patterns agents use BGP.tools API API for, with concrete tasks.

★ IP-to-ASN Enrichment Pipeline

Build an offline IP-to-ASN lookup service by ingesting the BGP.tools routing table once per hour and indexing the prefix-to-ASN map locally. The /table.jsonl endpoint streams every announced prefix with its origin ASN, which lets you classify any inbound IP address by its network owner. Typical setup time is under a day; the enrichment service can serve millions of lookups per second from memory.

Download /table.jsonl, parse each line into (prefix, asn) tuples, and build an in-memory radix tree for IP-to-ASN lookups.

Network Classification with Tags

Detect whether traffic originates from a hosting provider, anycast network, or government ASN by joining inbound IP addresses against BGP.tools tag lists. Tag membership is curated by the BGP.tools team and updated continuously; agents can pull /tags/{tagname}.csv for any tag listed in /tags.txt and use it to flag suspicious or expected traffic patterns.

Fetch /tags/hosting.csv and produce a deduplicated set of ASNs flagged as hosting providers.

Network Operator Reachability Reports

Generate a reachability report for a specific ASN by cross-referencing the BGP.tools routing table to find every prefix it currently originates. This is useful for network operators verifying their announcements are visible globally, or for security teams auditing the address space owned by a customer's ASN.

Filter /table.jsonl for entries where origin_asn equals 13335 and return the full list of prefixes Cloudflare announces.

AI Agent Network Forensics Assistant

An AI agent helping a SOC analyst can answer questions like 'who owns this IP?' and 'is this address space hosting infrastructure?' by calling BGP.tools through Jentic. The agent does not need to handle the User-Agent header convention manually — Jentic injects it from the stored credential. ASN context is returned as plain CSV or JSONL that the agent can summarise.

Search Jentic for 'asn name lookup', execute /asns.csv, and return the organisation name for ASN 15169.

Key Endpoints

6 endpoints — the bgp.

METHOD

PATH

DESCRIPTION

GET

/table.txt

Routing table as plaintext

GET

/table.jsonl

Routing table as JSONL stream

GET

/asns.csv

ASN to name mappings

GET

/tags.txt

List all available tags

GET

/tags/{tagname}.csv

Members of a tag as CSV

GET

/table.txt

Routing table as plaintext

GET

/table.jsonl

Routing table as JSONL stream

GET

/asns.csv

ASN to name mappings

GET

/tags.txt

List all available tags

GET

/tags/{tagname}.csv

Members of a tag as CSV

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The required User-Agent identifier is stored encrypted in the Jentic vault (MAXsystem). Agents call BGP.tools operations via Jentic and the User-Agent header is injected automatically — the agent never sees or transmits the raw value.

Intent-based discovery

Agents search by intent (e.g., 'lookup asn name') and Jentic returns the matching BGP.tools operation with its parameters and response shape, so the agent does not need to know which of the 6 endpoints to call.

Time to first call

Direct BGP.tools integration: half a day for User-Agent compliance, parsing CSV/JSONL, and caching. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shodan API

Shodan indexes hosts and services per IP, while BGP.tools focuses on routing-layer ownership.

Choose Shodan when you need open-port and service banners for an IP; choose BGP.tools when you need ASN ownership and prefix data.

Complementary

ipgeolocation.io API

ipgeolocation.io adds country, city, and timezone data to IP addresses identified via BGP.tools.

Pair with BGP.tools when an agent needs both network ownership and geographic context for an IP.

Complementary

AbuseIPDB API

AbuseIPDB returns abuse confidence scores for IPs that BGP.tools resolves to ASNs.

Use BGP.tools to identify the network owner and AbuseIPDB to check if the IP has a known abuse history.

FAQs

Specific to using BGP.tools API API through Jentic.

What authentication does the BGP.tools API use?

BGP.tools requires a custom User-Agent header on every request that identifies the caller (project name and contact email is the convention). The OpenAPI spec models this as an apiKey scheme on the User-Agent header. Through Jentic, the User-Agent value is stored encrypted in the Jentic vault and injected at execution time so the agent never sees the raw value.

Can I get the full BGP routing table from the BGP.tools API?

Yes. GET /table.txt returns the routing table in plaintext, and GET /table.jsonl returns the same data as newline-delimited JSON, which is more practical for streaming ingestion into a pipeline. Both endpoints cover the global IPv4 and IPv6 announced prefixes.

What are the rate limits for the BGP.tools API?

BGP.tools does not publish hard rate limits in the spec, but the operators ask for a real, contactable User-Agent and request that bulk consumers cache results rather than re-downloading the multi-megabyte table on every request. Refresh hourly at most for the routing table; tag lists change less frequently.

How do I look up an ASN through Jentic?

Search Jentic for 'asn name mapping' or 'GET /asns.csv', load the schema, and execute. With the SDK: pip install jentic, then SearchRequest, LoadRequest, and ExecutionRequest in an async flow — Jentic injects the configured User-Agent automatically.

Is the BGP.tools API free?

Yes — the data export endpoints are free for use as long as you provide a contactable User-Agent so the operators can reach you if your usage causes problems. There is no commercial tier specified in the OpenAPI spec.