Skip to main content

Pricing

Pay per screening with x402, or use a monthly key when request volume becomes predictable.

No account x402 pay-per-call
Steady volume Monthly API key
x402 pay-per-call

Screen first, pay only for the call.

Prompt screening
$0.005

POST /v1/parse

Output screening
$0.003

POST /v1/screen-output

Asset USDC
Network Base mainnet eip155:8453
Token 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Read x402 guide

x402 setup in four steps

1

Read prices

Call GET /v1/pricing and inspect accepts[].

2

Call endpoint

Send the screening request without a bearer key when using pay-per-call.

3

Sign USDC

Pay on Base mainnet with a scoped funded wallet.

4

Retry request

Retry with payment-signature; legacy clients may send x-payment.

Plans

Free
$0
forever
  • 10 req/min
  • 30-day key expiry
  • Self-service
  • 5 sandbox/hr
Generate Free Key
Most Popular
Pro
$49/mo
10K requests included
  • 60 req/min
  • $0.003/overage request
  • 50 sandbox/hr
  • Self-serve checkout
Start Pro
Team
$199/mo
50K requests included
  • 200 req/min
  • $0.002/overage request
  • 200 sandbox/hr
  • Priority support
Contact Sales
Enterprise
Custom
volume pricing
  • 1,000 req/min
  • Custom SLAs
  • 1,000 sandbox/hr
  • Dedicated support
Contact Sales

Cost Calculator

Estimate your monthly cost across plans. Drag the slider to set your expected request volume.

Free
$0
Pro
$49
Team
$199
x402
$50

Complete x402 endpoint prices

All x402 payments use USDC on Base mainnet. The screening calls most agents need first are $0.005 for /v1/parse and $0.003 for /v1/screen-output.

Endpoint Price (USDC) Description
POST /v1/parse $0.005 Screen untrusted input before an agent passes it to an LLM or tool.
POST /v1/screen-output $0.003 Screen LLM output before returning it to users, tools, memory, or other agents.
POST /v1/analyze $0.05 Run standard media credibility analysis.
POST /v1/evaluate $0.01 Evaluate prompt quality, safety, latency, and cost.
POST /v1/chat $0.005 Chat with Parse about analysis results and agent safety.

TypeScript

Use the current TypeScript x402 recipe at /skill#x402-node. It registers the required scheme before wrapping fetch.

Python

# pip install x402
from x402 import wrap_requests
session = wrap_requests(requests.Session(), wallet)
res = session.post("https://parsethis.ai/v1/parse", json={"prompt": "..."})

CLI

npx @x402/purl POST https://parsethis.ai/v1/parse -d '{"prompt":"..."}'

Should I use x402 or an API key?

Use Case Recommended Why
Autonomous first call or marketplace agent x402 No signup, pay per use
Development/testing Free API key No cost, instant setup
Production volume Pro/Team key Predictable rate limits and lower operational friction
Enterprise Enterprise key SLAs, custom limits

What endpoints are free?

  • GET /v1/models — list available LLM models
  • GET /v1/pricing — view x402 pricing info
  • POST /v1/keys/generate — generate a free API key
  • GET /skill — download the agent skill prompt
  • GET /llms.txt — LLM-readable documentation index
  • GET /health — service health check