Swarmio Billing API

The Billing API from Swarmio — 1 operation(s) for billing.

GitHub OpenAPI

Operations 1

GET /api/v1/billing/crypto Machine-payable top-up terms: network, asset, receiving address, rate, minimum. #

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/ioswarm-io:ioswarm-io-billing-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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

ioswarm-io-billing-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: SwarmIO Cloud Billing API
  version: 1.0.0
  description: 'The x402-payable and public agent surface of ioswarm.io — this root document is what agent discovery (x402scan register-origin, the agentcash probe) reads. The full contract, including the credit-billed account API (sk_swarm_ key), is at /api/v1/openapi.json; the human/agent doc is /llms.txt.


    AI that does real work for you. One POST kicks off a job that searches the web, reads sources, and writes a cited report; poll for the result.


    Agent onboarding (no browser, no human): 1) GET /api/v1/auth/config → Supabase url + anon key. 2) POST {supabase_url}/auth/v1/signup → access_token (email confirmation off). 3) POST /api/v1/agent/register → agent id. 4) POST /api/v1/account/api-keys → sk_swarm_ key (shown once). 5) Authorization: Bearer sk_swarm_… on everything else. Starter credits land automatically on the first authenticated call.


    The full agent doc is https://ioswarm.io/llms.txt; the A2A agent card is at /.well-known/agent-card.json; an MCP facade is at /mcp.'
  x-guidance: 'Agent surface. Paid x402 primitives answer a bare call with a 402 carrying the payment requirements (v1 in the body, v2 base64 in the PAYMENT-REQUIRED header): sign the EIP-3009 transferWithAuthorization they describe and re-send the identical request with X-PAYMENT (v1) or PAYMENT-SIGNATURE (v2). Paid per call: /api/v1/search ($0.02, 25 free/day), /api/v1/search/report ($0.05), /api/v1/news/brief ($0.05), /api/v1/market/price ($0.02, 10 free/day), /api/v1/video/transcript ($0.02, 10 free/day), /api/v1/video/search ($0.02, 25 free/day), /api/v1/x402/quote ($0.01), /api/v1/x402/fetch ($0.02), /api/v1/x402/chat ($0.02), /api/v1/feeds/{feed} ($0.01-$0.02; a free 24h-delayed edition sits at /api/v1/feeds/{feed}/sample). Long-running jobs: POST /api/v1/x402/run/{mode} ($0.25-$1.85 per run; the paying wallet becomes the account). Credit-billed account surface (API key, not x402): GET /api/v1/auth/config to discover the Supabase backend, sign up (email confirmation is off), POST /api/v1/agent/register, then POST /api/v1/account/api-keys for an sk_swarm_ key.'
  contact:
    url: https://ioswarm.io
    email: support@ioservices.io
servers:
- url: https://ioswarm.io
tags:
- name: Billing
paths:
  /api/v1/billing/crypto:
    get:
      operationId: getCryptoTerms
      summary: 'Machine-payable top-up terms: network, asset, receiving address, rate, minimum.'
      security: []
      responses:
        '200':
          description: Top-up terms. `enabled:false` means the operator has not published a receiving address yet.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CryptoTerms'
      tags:
      - Billing
components:
  schemas:
    CryptoTerms:
      type: object
      properties:
        enabled:
          type: boolean
        network:
          type: string
          example: base
        chain_id:
          type: integer
          example: 8453
        asset:
          type: string
          example: USDC
        contract:
          type: string
          example: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
        pay_to:
          type: string
          description: The receiving address — present only when enabled.
        min_usd:
          type: number
        credits_per_usd:
          type: number
        how:
          type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: An sk_swarm_ API key (long-lived; self-mint via /api/v1/account/api-keys) or a Supabase access_token (short-lived; from signup).