Frames Registry

Pay-per-call API gateway for AI agents. 8 services available via the x402 payment protocol. No API keys, no subscriptions — just pay per request with crypto.

Base URL

https://registry.frames.ag

Prerequisites

A crypto wallet funded with USDC is required to use paid endpoints. Two options:

• AgentWallet (recommended for agents) — server-side wallet that handles 402 detection, payment signing, and retries automatically via a single POST /x402/fetch call. No private key management needed on your side.
• Self-managed wallet — any EVM wallet (Base) or Solana wallet with USDC. You sign x402 payment headers directly.

Quick Start

1. Set up a wallet — create an AgentWallet or fund your own wallet with USDC
2. Discover services: GET https://registry.frames.ag/api/services
3. Read service docs: GET https://registry.frames.ag/api/service/{slug}/skill.md
4. Check pricing: GET https://registry.frames.ag/api/pricing
5. Make a paid request — via AgentWallet’s /x402/fetch or directly with x402 headers (see Payment Protocol below)

Services (8)

Service Endpoints

Each service lives at https://registry.frames.ag/api/service/{slug} and exposes:

Pricing Details

Twitter API (twitter)

Base: https://registry.frames.ag/api/service/twitter | Docs | OpenAPI | Skill

AI Generation API (ai-gen)

Base: https://registry.frames.ag/api/service/ai-gen | Docs | OpenAPI | Skill

x402 Test Service (test)

Base: https://registry.frames.ag/api/service/test | Docs | OpenAPI | Skill

Exa API (exa)

Base: https://registry.frames.ag/api/service/exa | Docs | OpenAPI | Skill

Wordspace Agent (wordspace)

Base: https://registry.frames.ag/api/service/wordspace | Docs | OpenAPI | Skill

Jupiter API (jupiter)

Base: https://registry.frames.ag/api/service/jupiter | Docs | OpenAPI | Skill

NEAR Intents API (near-intents)

Base: https://registry.frames.ag/api/service/near-intents | Docs | OpenAPI | Skill

AI Model Pricing (ai-gen)

Price is set dynamically based on the model field in the request body.

Image Models:

Video Models:

Payment Protocol (x402)

All paid endpoints use the x402 payment protocol. No API keys needed.

Flow:

1. Call any paid endpoint without a payment header
2. Receive 402 Payment Required with a PAYMENT-REQUIRED header (Base64 JSON with price, network, payTo address)
3. Sign a payment for the requested amount on your chosen network
4. Retry the same request with the PAYMENT-SIGNATURE header
5. Receive the response plus a PAYMENT-RESPONSE confirmation header

Failed requests are automatically refunded.

Supported Networks:

Accepted Tokens: USDC, USDT, CASH (availability varies by network)

Platform Endpoints (FREE)

Agent Integration

With AgentWallet (recommended)

AgentWallet is a server-side wallet for AI agents. It manages keys, balances, and x402 payment signing so agents don’t need to handle crypto directly.

1. Authenticate with AgentWallet (email OTP → API token)
2. Fund your wallet with USDC on Base or Solana
3. Call any Frames Registry endpoint through AgentWallet’s proxy:

POST https://frames.ag/x402/fetch
{
  "url": "https://registry.frames.ag/api/service/twitter/api/search-tweets",
  "method": "POST",
  "body": { "query": "AI agents" }
}

AgentWallet detects the 402 response, signs payment, and retries automatically.

Direct x402 (self-managed wallet)

Requires an EVM or Solana wallet with USDC and the ability to sign EIP-3009 or SPL transfers.

1. Make the request to the paid endpoint
2. Parse the PAYMENT-REQUIRED header from the 402 response (Base64 JSON with price, network, payTo)
3. Sign a payment authorization for the exact amount
4. Retry with the PAYMENT-SIGNATURE header