Skip to main content
Proceeds has five primitives. You configure the first two; the next three are emitted automatically as your paywalls run.

​
Service

A Service groups related endpoints under one configuration. Use one service per API product. A service defines:
  • Base URL — the upstream origin Proceeds proxies to
  • Mode — Testnet or Mainnet
  • Networks — payment-capable chains accepted by every paywall in the service
  • Auth method — credentials Proceeds attaches to upstream requests, kept inside Proceeds and never exposed to the client
  • Discovery metadata — categories, docs links, public routes, and agent guidance published in OpenAPI discovery documents. See API discovery.
Supported upstream auth methods: none, bearer, token, x-api-key, custom-header, query-param, bearer-customer, x-api-key-secret, json-body-field. See Forward upstream auth.

​
Paywall

A Paywall protects one route on a service. You set the price; Proceeds enforces it. A paywall defines:
  • Slug — appears in the public URL
  • Target URL — the upstream path Proceeds proxies to
  • Allowed HTTP methods — GET, POST, PUT, PATCH
  • Price — in USDC
  • Networks — chains accepted for this endpoint
  • Custom headers and query parameters — forwarded to the upstream
  • Enabled state
Each paywall exposes generated URLs:
Paywalls run as a proxy (targetType: "PROXY"). Proceeds is the payment gate and the request proxy; your origin is unchanged.

​
Transaction

A Transaction is one payment attempt against a paywall. Transactions move through these states: Inspect transactions →

​
Event

An Event is a single step in a request’s lifecycle. Proceeds emits three event types:
  • REQUEST — paywall hit without payment (402 path)
  • SUCCESS — successful payment and fulfillment
  • ERROR — settlement or upstream failure
Use Events to debug where a flow stopped: did the request reach the paywall, did payment and fulfillment complete, or did settlement/upstream fail? Trace events → To be notified of events on your own server instead of inspecting them in the dashboard, configure Webhooks.

​
Wallet

A Wallet view shows balances across rails and chains. Withdraw onchain per holding, or set Destination to Bank (ACH) to off-ramp USDC to a US bank account via Bridge. See balances → · Settlement →

Supported blockchains

Networks and testnet vs mainnet mode.

API discovery

Help agents find and pay your endpoints.