Docs

x402 Asset API

VideoSync already exposes x402-compatible payment flows for subscription unlocks, API access unlocks, and delivery HD unlocks. This page explains the currently implemented endpoints, the payment flow, and how to adapt them into marketplace-ready asset APIs.

Open API Access Page Request a Custom API Demo

What Exists Today

Implemented x402 flows

GET /api/subscribe/unlock-spec

Returns x402 payment requirements for the creator subscription flow.

POST /api/subscribe/unlock

Accepts the signed X-Payment payload and activates the paid subscription.

GET /api/api-access/unlock-spec

Returns x402 payment requirements for API access tiers.

POST /api/api-access/unlock

Settles API tier payment and unlocks the selected key tier.

GET /delivery/:id/unlock-spec

Returns the HD-unlock price and payment requirements for a delivery preview page.

POST /delivery/:id/unlock

Settles the delivery unlock payment and returns 30-day HD access metadata.

Payment Flow

How a client unlocks a paid resource

The client requests an `unlock-spec` endpoint first.
VideoSync returns x402 payment requirements for a Base USDC transfer.
The wallet signs the payment authorization.
The signed payload is sent back in `X-Payment` to the matching `unlock` endpoint.
VideoSync settles the payment and returns the unlocked resource metadata.

Headers & Payloads

Minimum integration contract

Request headers

Content-Type: application/json
X-Payment: <signed x402 payload>

Example resource pattern

GET  /delivery/:id/unlock-spec
POST /delivery/:id/unlock

GET  /api/subscribe/unlock-spec
POST /api/subscribe/unlock

Roadmap

Next endpoints to expose as true asset APIs

`POST /api/x402/generate-thumbnail-pack`
`POST /api/x402/generate-product-mockup`
`POST /api/x402/generate-landing-hero-video`
`POST /api/x402/generate-narrated-explainer`
`POST /api/x402/enrich-creator-lead`

These are the most marketplace-friendly next steps because they have clean per-call economics and don’t require exposing the entire editing studio at once.