Nautilinks Developers

An API built for humans and agents.

Search the Nautilinks catalog, prepare an order, track a publication, or connect an MCP client directly. REST, MCP and the CLI share the same account, prices and safeguards.

OpenAPI 3.1 Detailed documentation

REST quickstart

Make your first call in under a minute

  1. Create a Nautilinks account, then generate an sn_test_… key in the member area to work in the sandbox.
  2. Send the key only in the Authorization: Bearer … header. Never put it in a URL or repository.
  3. Query the catalog. A sandbox key uses real inventory and prices, but a simulated order never charges funds or creates a publisher order.
export NAUTILINKS_API_KEY="sn_test_…"

curl --fail-with-body \
  -H "Authorization: Bearer $NAUTILINKS_API_KEY" \
  "https://nautilinks.co/api/v1/agent/catalog?q=voyage&limit=5"

Live writes require an sn_live_… key. An order may spend prepaid credit; always have the human confirm sites, anchors, target URLs and budget before the live call. Reuse the same Idempotency-Key after a timeout.

Official interfaces

Choose the right contract for your agent

Nautilinks OpenAPI 3.1

The complete REST API contract: unique operationIds, typed parameters, request and response schemas, authentication, and structured errors.

Open openapi.json →

Nautilinks MCP server

The remote MCP server exposes catalog, articles, balance, ordering and tracking over Streamable HTTP.

Read the MCP guide →

API authentication

Create, store and send Bearer keys; read/order scopes; and sandbox versus live behavior.

Authenticate a client →

Webhooks Nautilinks

Subscriptions, order events, HMAC-SHA256 verification, replay protection and revocation.

Integrate webhooks →

Versioning and rate limits

v1 stability, RateLimit headers, 429 errors, deprecation notice and sunset policy.

Read the API policy →

Agent instructions

Recommended use cases, limits, minimal call flow, pre-purchase confirmation and key protection.

Read agent instructions →

Official CLI

Dependency-free Node.js client for searching, comparing, ordering and tracking from a terminal or automation.

Download the package →

MCP Streamable HTTP

Native connectivity for agents

The remote endpoint is https://mcp.nautilinks.co/mcp. Initialization and the public about tool work without a key; business tools use a Nautilinks Bearer key. Read the Nautilinks MCP guide and public manifest.

Webhooks

Track without polling

Register a public HTTPS URL through the API. Nautilinks signs order events; verify the signature before processing, make your consumer idempotent, and return a 2xx promptly. The Nautilinks webhook guide documents the exact calculation.

Predictable errors

Machine-readable JSON for recovery

Every API error returns ok, error, code, message and resolution. Responses also expose their real-time quota. An agent can correct its call or wait for Retry-After without parsing HTML.

Developer support

Need integration help?

Email contact@nautilinks.co or use the contact page. Include your MCP client, operation, error code and request ID — never your secret key.