run402-com Billing API

Prepaid allowance accounts and checkout

Operations 17

POST /agent/v1/lightning-wallet Mint the caller's Lightning wallet #
GET /agent/v1/lightning-wallet Read the caller's Lightning wallet #
DELETE /agent/v1/lightning-wallet Revoke the caller's Lightning wallet #
GET /wallets/v1/{address}/projects List projects by wallet #
GET /wallets/v1/{address}/label Read a wallet's display label #
POST /wallets/v1/{address}/label Set a wallet's display label #
GET /orgs/v1/lookup Look up organization billing state #
GET /orgs/v1/{org_id}/billing Get organization billing state #
GET /orgs/v1/{org_id}/billing/history Get organization transaction history #
GET /orgs/v1/email Look up a organization by wallet or email #
POST /orgs/v1/email Create an email-based organization #
POST /orgs/v1/{org_id}/wallets Link a wallet to an email organization #
POST /orgs/v1/{org_id}/checkouts Create a checkout for an organization: a Stripe session, or a Lightning invoice… #
GET /orgs/v1/{org_id}/checkouts/{topup_id} Read one top-up (the Lightning waiting client's poll) #
PATCH /orgs/v1/{org_id}/billing/auto-recharge Enable or disable email pack auto-recharge #
PATCH /orgs/v1/{org_id}/billing/metering Enable or disable prepaid metered usage under one monthly cap, and the card… #
POST /orgs/v1/{org_id}/billing/payment-methods/setup Save a card for the standing order (a Stripe Checkout session in setup mode) #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/run402-com:run402-com-billing-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

run402-com-billing-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Run402 Billing API
  version: 2.0.0
  description: 'Full-stack infrastructure for AI agents. Postgres, REST API, auth, file storage, static site hosting, serverless functions. Tier payments and image generation use the shared payment engine: x402 (USDC on Base), MPP on Tempo (pathUSD), and the draft-pinned MPP Lightning charge profile (sats, Bitcoin mainnet) for authenticated tier purchases and image generation.'
  contact:
    name: Run402
    url: https://run402.com
  guidance: 'Run402 is a pay-per-use backend for AI agents: Postgres databases, static hosting, serverless functions, and image generation. The shared payment engine supports x402 (USDC on Base), MPP on Tempo (pathUSD), and the exact Run402 MPP Lightning charge profile on Bitcoin mainnet (sats).


    ## Quick start

    1. Install the CLI: npm install -g run402@latest

    2. Create an allowance: run402 init

    3. Set the prototype tier (FREE, testnet USDC): run402 tier set prototype

    4. Provision a project: run402 projects provision --name "my-app"

    5. Deploy: run402 deploy --manifest app.json


    ## Payment model

    - Tiers (prototype $0.10 testnet, hobby $5, team $20; hobby and team are 30-day prepaid leases) unlock all platform features.

    - Image generation is $0.03 per call (x402, MPP on Tempo, or MPP Lightning micropayment).

    - Auth-only endpoints (projects, deploys, messages) require SIWX wallet identity but no payment.


    ## Auth

    - x402 endpoints: include a payment header (handled automatically by the CLI or x402 client libraries).

    - Explicit MPP Lightning tier requests require the exact Run402 profile, ordered Accept-Payment preferences, one principal credential, a stable Idempotency-Key, and buyer-side USD/native/fee limits.

    - SIWX endpoints: sign a CAIP-122 message with your wallet.

    - REST API: use the project''s anon_key or service_key as the apikey header.


    ## Client metadata

    - Recent Node SDK/CLI clients may send Run402-Client: surface="cli", version="3.7.14", sdk="3.7.14". It is advisory, bounded, never used for auth/billing/trust, and not browser-CORS-enabled yet.


    ## Docs

    - Full CLI docs: https://run402.com/llms-cli.txt

    - API docs: https://run402.com/llms.txt'
servers:
- url: https://api.run402.com
  description: Production
tags:


# --- truncated at 32 KB (61 KB total) ---
# Full source: https://artifacts.apis.io/run402-com/openapi/run402-com-billing-api-openapi.yml