How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Primitive Payments API

Collect and pay stablecoin (USDC) payments with x402. Settlement isnon-custodial: funds move directly from payer to payee on-chain via anEIP-3009 authorization the payer signs with their own key, and Primitivenever holds funds. The payee registers a payout address and creates achallenge; the payer signs and settles it under a configurable spendpolicy (kill-switch, per-payment and per-day caps, payee allowlist).

Primitive Payments API is one of 22 APIs that Primitive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 9 operations across 7 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.primitive.dev/v1.

9 operations 7 paths 3 schemas 4 GET4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
https://api.primitive.dev/v1
Authentication
HTTP Bearer, API Key
Contact
Resource Areas
1

Authentication & Security 2

Primitive Payments API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). An API key is passed in the query as token (DownloadToken).

  • BearerAuth — API key with prim prefix or OAuth access token with primoat prefix: Authorization: Bearer . Access is governed by the caller's organization role (owner, admin,…
  • DownloadToken — Signed download token provided in webhook payloads

Paths & Operations 9

Across 7 paths, the API surfaces 9 operations — 4 GET, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Payments 9

Collect and pay stablecoin (USDC) payments with x402. Settlement is non-custodial: funds move directly from payer to payee on-chain via an EIP-3009 authorization the payer signs w…

POST
/x402/payout-addresses
Register a payout address
registerPayoutAddress 1 param body → 201400401403422429
GET
/x402/payout-addresses
List payout addresses
listPayoutAddresses → 200401403429
POST
/x402/email-challenges
Create an email-native payment challenge
createEmailChallenge 1 param body → 200201400401403409422429
POST
/x402/challenges
Create a payment challenge
createChallenge 1 param body → 201400401403422429
GET
/x402/challenges/{id}
Get a payment challenge
getChallenge 1 param → 200400401403404429
POST
/x402/challenges/{id}/pay
Pay a payment challenge
payChallenge 2 params body → 200400401403404409422429
GET
/x402/spend-policy
Get your spend policy
getSpendPolicy → 200401403429
PUT
/x402/spend-policy
Update your spend policy
updateSpendPolicy body → 200400401403429
GET
/x402/declined-payments
List declined payments
listDeclinedPayments → 200401403429

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are GateDenial (6 properties), ErrorResponse (2 properties), GateFix (2 properties). Each schema is shown below with its type and property counts.

GateFix
object
2 properties 2 required
ErrorResponse
object
2 properties 2 required
GateDenial
object
6 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

primitive-payments-api-openapi.yml Raw ↑

Other APIs Primitive publishes across the network.

Primitive Account API
Primitive Agent API
Primitive CLI API
Primitive Demo API
Primitive Discovery API
Primitive Domains API
Primitive Emails API
Primitive Endpoints API
Primitive Filters API
Primitive Functions API
Primitive Inbox API
Primitive Memories API
Where this information came from

This is an independent, third-party profile of Primitive Payments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.