API versioning
How Starcovery versions REST and MCP, and how deprecation is signaled.
Starcovery REST and MCP are version 1. Send the optional API-Version header with value 1. Responses echo API-Version: 1.
Paths stay under /api without a /v1 prefix. A breaking change increments API-Version. Starcovery does not keep a parallel old path after a break.
Deprecation
When an operation is removed, responses for that operation send Deprecation and Sunset (RFC 8594 and RFC 9745). The OpenAPI description at /openapi.json is the live contract. Documented operations that are gone are deleted from that file rather than left as shims.
Rate limits
Unsigned GET /api/search includes 10 requests per rolling 24 hours per client IP. Identified search includes 20 requests per rolling 24 hours per user, then prepaid extra credits. Query parse allows 50 requests per 60 seconds. Responses send API-Version, RateLimit-Limit, and RateLimit-Policy. When the limiter reports remaining, responses also send RateLimit, RateLimit-Remaining, and RateLimit-Reset. A parse 429 also sends Retry-After. The parse quota name is parse. The search quota name is search. Success responses do not send Retry-After.
Test call
Unsigned search is the live test call. No separate sandbox host:
curl "https://www.starcovery.com/api/search?q=slow+morning+coffee"