Authorization
secretKey AuthorizationBearer <token>
Server-side sk_ key. Grants a subset of the merchant's permissions.
In: header
Response Body
application/json
application/json
curl -X GET "https://example.com/v1/x402/resources"{ "resources": [ { "id": "string", "merchantId": "string", "url": "string", "description": "string", "mimeType": "string", "price": { "amount": "string", "asset": "string", "formatted": "string", "display": "string" }, "maxTimeoutSeconds": 0, "listed": true, "accepts": [ { "chain": "string", "asset": "string", "contract": "string", "payTo": "string", "transferMethod": "string", "domain": { "property1": null, "property2": null } } ] } ]}Receive a provider webhook
Provider callback surface. Integrators normally configure outbound merchant webhooks in the dashboard instead of calling this operation. The raw body is passed to the adapter so signatures verify over exactly the signed bytes.
Register a resource
Register or re-register an endpoint this merchant hosts, so Mayarin can quote it and settle for it. The `url` must be the exact URL an agent will call — scheme, host and path all count, because a resource is identified by it. The token's EIP-712 domain and transfer method are read off the contracts at registration, never entered.