Skip to main content
Canonical OpenAPI JSON · Version 1 OpenAPI JSON The Altss public interface returns catalog metadata, JSON Schema documents and bounded published profile summaries. Every documented operation has a unique operationId, typed inputs and responses, and security: []. This does not grant premium-data access. It declares no OAuth issuer, API-key provisioning or private intelligence endpoint. Public SDK/CLI installation and REST, MCP, NLWeb and A2A connection details are at https://altss.com/developers. Catalog errors include ok=false, code, error and resolution; public profile errors use ok=false, code and error. Inspect the per-operation schemas. Unknown schemas or published profile slugs return 404; unsupported methods return 405. HEAD has no body. Only descriptive catalogs support conditional 304. Profile reads are private/no-store and expose instance RateLimit headers. Batch items report their own status. Infrastructure/network failures remain separate from application errors.

​
Versioning and deprecation

The public interface uses URL major versions. /api/v1 provides descriptive catalogs, JSON Schema documents, bounded public profile reads and durable checks of four fixed public integration metadata documents. Public check jobs accept no profiles, supplied URLs or application data. Original root catalog URLs remain supported aliases; production profile reads and metadata check jobs exist only under /api/v1/public. /api/v1/sandbox/public uses the same profile contract with fictional fixtures, separate instance budgets and replay caches, and no production queries. /api and /api/v1 describe the available public interfaces. The contract version describes response structure, not a frozen price, coverage count or record-verification date. Breaking response-shape changes require a new URL major version. Within v1, existing fields retain their types and meaning. Changes that would invalidate a response against the v1 contract belong in a new major version. Catalog values and their own version or update dates can change within that contract without a transport-version change. No published public descriptive endpoint is currently deprecated or scheduled for removal. Before retiring a supported endpoint, publish a migration notice and replacement, signal deprecation with the Deprecation header (RFC 9745), and use Sunset (RFC 8594) only when an actual withdrawal date has been announced. Supported aliases are not silently redirected to a different major version. Public reads do not create orders or change records. Use ETag / If-None-Match for catalog descriptions; public profile reads are private/no-store. The read-only profile batch optionally accepts Idempotency-Key with 120-second per-instance replay retention, not durable or global exactly-once processing. Retry temporary failures with backoff. No payment, bulk export or private-data entitlement is provided.

​
Website checkout retries

The website’s standard-plan checkout start is separate from this public descriptive interface. It accepts a UUID Idempotency-Key header as the existing requestId; if both are supplied, they must match. Retry the same attempt with the same key and unchanged details. A changed request under an existing identity returns 409 rather than creating another order. Invalid keys return 400; header/body identity conflicts return 409 before any order is recorded. Existing body-based clients remain supported. Approval-derived Emerging Manager checkouts keep their existing private-link identity and reject the optional header. Same-origin JSON, purchaser authorization, current terms acceptance and every existing validation still apply. Starting or retrying checkout does not itself charge a payment method. Public machine interface guide