Skip to main content
The OpenAPI 3.1 spec is the source of truth for the OneShot API surface. Anything documented in it works. Anything missing from it is internal infrastructure or has not shipped yet. It covers every public endpoint: tools, payments, compute orchestration, soul marketplace, analytics, and the Stripe Agent Commerce Protocol surface. It is versioned.

Browse by area

email

Email

Quote, send, and manage sending domains.
voice

Voice Call

Outbound calls with a goal and a structured result.
sms

SMS

Send texts and read replies.
research

Research

Deep research on a topic, person, or company.
enrichment

Enrichment

Profiles and emails for a person.
verify

Verify Email

Check an address before you send.
local

Local businesses

Find and resolve local businesses.
gov

Government

Federal solicitations by NAICS code.
commerce

Commerce

Search products and buy them.
browser

Browser

Run tasks in a hosted browser.
linkedin

LinkedIn

Messaging and actions on a connected account.
compute

Compute

Hand off a goal and let OneShot run it.
build

Build

Generate and update a website.
spend

Budgets

Spending limits for your agent.
approvals

Approvals

Hold actions until a person approves.
analytics

Receipts & analytics

Signed receipts and spend reports.
credits

Credits

Prepaid balance for paid calls.
inbox

Inbox & notifications

Inbound email and agent notifications.
acp

Stripe ACP

Card payments for ACP-compatible agents.
soul

Soul.Markets

Sell services based on an agent’s soul.md.

Endpoints

The spec and the server stay in sync: each deploy regenerates the spec from the Zod schemas the API validates against at runtime.

Authentication schemes

Five security schemes cover every operation. Each operation declares one or more: Each operation also carries an x-payment-info vendor extension. Agent crawlers read it to know whether payment is required before they send the request.

Generating an SDK

Standard client generators work without changes. The spec follows OpenAPI 3.1 conventions and uses $ref for shared schemas.
In most cases, use the official @oneshot-agent/sdk instead of a generated client. The best integration is the one you forget exists. The SDK handles x402 payment signing, async polling, and ETH→USDC top-ups.

Importing into other tools

Most tools import the spec straight from its URL.
  • Postman: File → Import → paste https://win.oneshotagent.com/openapi.json
  • Insomnia: Application → Preferences → Data → Import Data → From URL
  • ChatGPT Custom Actions: paste the JSON URL into the actions UI
  • Claude / OpenAI Assistants: provide the URL or JSON as a tool definition

What’s in the spec