Look up IP/ASN registration data via ARIN RDAP and manage records via Reg-RWS
domain: arin.net · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
For read-only lookups, query ARIN's RDAP service with no authentication, e.g. GET https://rdap.arin.net/registry/ip/<address or prefix> or /registry/autnum/<asn>, receiving standard RDAP-format JSON instead of legacy free-text WHOIS.
For write operations (creating/modifying network, org, POC, or delegation records), use the separate Reg-RWS API instead, authenticating by appending ?apikey=<key> as a query parameter on every call.
Map HTTP verbs to Reg-RWS operations directly: GET retrieves, POST creates, PUT modifies, DELETE removes, using handle-based paths like /rest/net/<NET-HANDLE>/customer.
Test Reg-RWS calls against ARIN's OTE (Operational Test & Evaluation) sandbox environment before running them against production.
Poll the Tickets methods for status, since creating or modifying an Org- or NET-affecting record generates an ARIN-reviewed ticket rather than completing instantly.
Known gotchas
Reg-RWS API keys are tied to a specific POC (Point of Contact) role — the key's owner must be the Admin or Tech POC for the relevant Org, or write calls fail with a permission error.
Reverse DNS delegation changes made via Reg-RWS can take up to 24 hours to actually propagate, per ARIN's own documentation.
RDAP (read, no auth) and Reg-RWS (write, API-key auth) are entirely separate systems with separate hosts — don't expect RDAP data to be writable or Reg-RWS to work without a key.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?