Marketplace & buyer API

The marketplace is how AI companies license content across every Oasy
publisher without one-off negotiations. Browse it at
/marketplace; manage
everything in the buyer portal
or over the API below.

All endpoints live on the platform origin and (except signup/catalog) take
Authorization: Bearer mk_….

Get a key

POST /api/marketplace/signup
{ "name": "AgentCo AI", "email": "[email protected]" }
→ { "buyerId": "…", "apiKey": "mk_…" }     // shown once — store it

Rotate (= revoke) it anytime; the old key stops working immediately:

POST /api/marketplace/rotate-key            → { "apiKey": "mk_…" }

Discover the catalog

GET /api/marketplace/catalog

Every publisher with content: article counts, granted rights per use case,
per-use pricing, MCP endpoint, license-terms URL — plus the standard rate
card.

Two billing modes

1. Metered pay-per-use (default — nothing to set up). Your key (over
REST) and your registered MCP installs may read per-use-priced content
immediately. Each read accrues a charge at the publisher's advertised
per-use price, settles on your monthly statement, and is hard-capped at
$1,000 per publisher per month — past the cap you fall back to the
rights you actually hold (usually summary-only).

2. Prepaid subscription. A flat monthly license per publisher at the
platform rate card — no negotiation:

Component	Monthly
Base access	$50.00
+ `summarization`	$10.00
+ `display`	$50.00
+ `rag`	$25.00

(fine_tuning is never in the standard bundle — request it per publisher
via the request_license workflow.)

POST /api/marketplace/licenses
{ "publisherId": "…", "useCases": ["summarization", "display", "rag"] }

With Stripe configured you get back a checkoutUrl (monthly subscription;
the license activates when you land back on the portal). Subscriptions
suppress per-use charges for the use cases they cover.

Register your MCP installs

POST /api/marketplace/clients
{ "clientId": "<client_id from your install's OAuth registration>" }

Licenses and metered billing then apply to that install's MCP traffic.
A virtual install (buyer:<id>) is created at signup so plain REST calls
with your key are covered automatically.

Usage & settlement

GET /api/marketplace/usage?days=30
→ { "usage": [per-publisher calls/reads/paywalls], "metered": [per-publisher spend], "meteredTotalCents": … }

GET /api/marketplace/statement
→ one consolidated monthly statement: subscription fees + metered lines + total

Statements are currently settled by invoice; automatic card collection is
coming. Production access at volume is backed by a signed platform
agreement.