OpenAPI specification
These operations require no authentication. Catalogs return public descriptions; /api/v1/public provides bounded published profile name search, individual reads and a five-profile read batch with canonical citations. Private intelligence, customer records, authenticated graph queries, enrichment and paid-task execution are not offered through this interface. The website commercial form is not a task-execution API.
Reference
Altss Public Machine Interfaces
Read public metadata and contract descriptions; operational intelligence remains protected.
Public website catalogs, schemas and bounded published profile summaries require no authentication. The descriptive catalogs do not execute tasks. The /public paths provide limited public name search and profile reads with canonical citations. No premium intelligence, authenticated graph queries, bulk extraction, customer data or automated paid-task execution is exposed. This specification declares no API key, OAuth scope or machine authentication issuer. Website commercial forms are excluded. Platform network, WAF and gateway errors are outside the application JSON error contract. 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.