REST API Reference

The OneStop /v1 REST API is the direct-call surface behind agent spending. Use it when an agent or integration already has a workspace API key and needs to search the catalog, read listings and entitlements, or invoke an API listing.

Authenticate with a workspace API key as a bearer token: Authorization: Bearer osk_.... Spend is governed by the key's policy and caps; discovery and read endpoints (search, details, entitlements) work without wallet funds, while paid invocations fail with 402 if the workspace wallet is empty. Every endpoint below is relative to this base URL:

Endpoint:
https://api.onestop.sh

Direct call flow

  1. Obtain a workspace API key from the dashboard, or ask a permitted agent to mint one via MCP.
  2. Use the endpoints below for catalog search, listing details, and entitlements.
  3. For API listings, first inspect the listing, fetch its listing-specific OpenAPI spec_url, then call the operation through the gateway server declared in that spec.

MCP is optional for direct REST calls. MCP helps agents discover listings and read product_details; REST is the surface that actually invokes API listings.

  • POST/v1/search

    Semantic + lexical catalog search

  • GET/v1/details/{vendor_slug}/{listing_slug}

    Listing detail — resolved spec_url, formatted prices, and an invoke runbook

  • GET/v1/entitlements

    Items the workspace owns

OpenAPI spec

Download or copy the full machine-readable spec for the core OneStop /v1 endpoints to generate a client or import it into your tooling. API listings publish their own specs separately; get those from /v1/details/{vendor_slug}/{listing_slug} or product_details.endpoints.spec_url.

Download spec

Invoking API listings

API listings are called through the OneStop gateway:

/v1/invoke/{vendor_slug}/{listing_slug}/…

Each listing publishes its own OpenAPI spec — its operations, parameters, and pricing live there. Grab a listing's spec from /v1/details/{vendor_slug}/{listing_slug} (or the product_details MCP tool's endpoints.spec_url) and codegen against it; its servers already point at the gateway.