Version stability
The current base URL is https://nautilinks.co/api/v1/agent/. Compatible additions—new optional properties, operations, enum values, or error codes—may ship within v1. Removing or changing an existing field, operation, authentication rule, or meaning requires a new URL version. Every response includes Nautilinks-API-Version: 1.
Deprecation and sunset
API v1 is active and is not deprecated. When Nautilinks deprecates a version, affected responses will include an RFC 9745 Deprecation header containing the deprecation date, an RFC 8594 Sunset header containing the final service date, and a Link with rel="deprecation" pointing to migration guidance.
Nautilinks will normally provide at least 90 days between a public deprecation notice and sunset. A shorter window is reserved for urgent security, legal, or abuse-prevention changes; the migration page will explain the exception.
Rate limits
The Agent API allows 600 requests per 60-second fixed window per client IP. Responses expose the current IETF HTTPAPI structured fields RateLimit-Policy and RateLimit, plus compatibility aliases. A quota response is HTTP 429, uses the standard typed JSON error model, and includes Retry-After. Agents must stop and wait for that duration; they must not retry in a tight loop.
RateLimit-Policy: "agent-api";q=600;w=60
RateLimit: "agent-api";r=599;t=42
Nautilinks-API-Version: 1
Link: <https://nautilinks.co/en/developers/versioning/>; rel="deprecation"The separate rolling daily order cap protects purchasing. Reaching it also returns 429 and Retry-After; it does not authorize an agent to switch keys or accounts to bypass the limit.