Home Product Docs Pricing AI Integrations Blog About 𝕏 @Datavor_ai ▶ YouTube
Get Started — Free →
Available v3.2 · Pay only for what you use

Agent Pricing.

For autonomous AI agents calling Datavor through API keys. Metered per tool call, settled in USDC or Stripe. No subscription, no seats — every key starts with $5 in free credits, then top up from $10.

⬡ Light
$ 0.001 /call
20 tools
Reads and metadata. List connections, describe tables, fetch dashboards, check CDC status, inspect context. Cheap because we cache aggressively.
⬡ Standard
$ 0.005 /call
20 tools
Queries, transform previews, connection setup, and scheduler management. Real database work but no bulk data movement.
⬡ Heavy
$ 0.05 /call
7 tools
Sync, CDC streams, and scheduled job execution. Calls that move bulk data — we charge for it because we measure for it.

What a typical day costs

Light: 50 calls × $0.001 = $0.05
Standard: 20 × $0.005 = $0.10
Heavy: 5 × $0.05 = $0.25
$0.40 / day
An active agent doing real work · ≈ $12 / month

Which tools are in which tier?

Every one of Datavor's 50 MCP tools is mapped to a tier. The tier reflects the actual cost of executing the call — light tools read cached metadata, heavy tools move data.

Light $0.001 / call 20 tools

Metadata reads, listings, and status checks. Almost free.

ToolWhat it does
list_connectionsList all active connections
close_connectionClose a connection
list_tablesList tables with row counts
describe_tableShow columns, types, constraints, FKs
compare_table_schemasSide-by-side column comparison
show_database_treeHierarchical table / column view
analyze_schema_diffFind differences between schemas
recommend_sync_orderAI priority suggestions
scheduler_list_jobsList all scheduler jobs
scheduler_show_graphRender scheduler dependency graph
dashboard_summaryOverview: success rate, rows, trends
dashboard_table_historyRun log for a specific table
dashboard_failuresFailures with error messages
get_contextGet everything Datavor knows about a DB
explain_databaseNatural language summary of a database
list_recipesList saved transform recipes
get_suggestionsGet pending suggestions
cdc_statusInspect CDC stream status and lag
register_proRegister for Pro activation
activate_proActivate Pro with a code

Standard $0.005 / call 20 tools

Data reads, transform previews, scheduler management. Real work without bulk movement.

ToolWhat it does
connect_mysqlConnect to a MySQL database
connect_postgresConnect to a PostgreSQL database
connect_sqlserverConnect to a SQL Server database
connect_sqliteConnect to a SQLite file
connect_snowflakeConnect to Snowflake
execute_queryRun any SQL query
get_table_dataFetch rows from a table
transform_previewPreview transforms on sample data
add_ruleSave a business rule
update_ruleUpdate an existing rule
remove_ruleDelete a rule
save_recipeSave a transform recipe
apply_recipeApply a recipe to a sync config
accept_suggestionAccept a pending suggestion
dismiss_suggestionDismiss a pending suggestion
scheduler_create_jobSave a sync job with a schedule
scheduler_pause_jobPause a scheduled job
scheduler_resume_jobResume a paused job
scheduler_delete_jobDelete a job permanently
scheduler_add_dependencyAdd a job dependency (DAG)

Heavy $0.05 / call 7 tools

Calls that move data or change persistent state. Priced honestly because the resource cost is real.

ToolWhat it does
sync_tableSync a full table between two databases
sync_table_partialSync rows matching a WHERE clause
sync_table_incrementalSync only new/updated rows
sync_table_with_transformsSync with inline transforms
start_cdcStart a real-time CDC stream
stop_cdcStop a running CDC stream
scheduler_run_jobRun a scheduled job immediately

How it works

Run datavor serve on your own machine — that's the MCP endpoint your agent talks to. Datavor doesn't host one, and we never see your queries, rows, or credentials. The local server is just the auth + metering boundary: it validates your dvpro_agent_* bearer on session start and records each tool call with our billing backend. That's the only thing that leaves your infrastructure.

Request a key

Email agents@datavor.ai with the wallet address you'll fund from. We issue a dvpro_agent_* key with $5 in free credits — enough for ≈ 1,000 Standard calls or 100 Heavy calls — and bind your wallet so USDC top-ups credit the right key.

Top up your balance

When credits run low, top up from $10 — USDC on Base (send from your registered wallet to the deposit address we provide) or by card via Stripe. Auto-recharge optional — set a threshold, we'll refill. See the exact command →

Call any MCP tool

Your agent POSTs to your local server with Authorization: Bearer dvpro_agent_*. The local server runs the tool against your data and reports usage to our billing backend. When your balance can't cover the next call, the server returns 402 Payment Required and the agent pauses until you top up.

Example — run your own instance, then point your agent at it # 1. Start the HTTP transport on your own infrastructure. There is no # Datavor-hosted endpoint — you run Datavor where your data lives. # Default port is 4747. Use --port 0 for a random free port; the # post-listen banner echoes the resolved URL so you can paste it # into your agent's MCP client config. npx datavor serve # → Streamable HTTP on http://localhost:4747/mcp # 2. Your agent POSTs MCP tool calls to YOUR instance. The agent's key # rides in the Authorization header and is metered per call. curl -X POST http://localhost:4747/mcp \ -H "Authorization: Bearer dvpro_agent_a1b2c3d4..." \ -H "Content-Type: application/json" \ -d '{ "tool": "sync_table", "input": { "source": "prod-mysql", "target": "analytics-pg", "table": "orders" } }' # Response includes billing metadata HTTP/1.1 200 OK { "result": { "rows_synced": 12847, "duration_ms": 8421 }, "billing": { "tier": "heavy", "charged_usd": 0.05, "balance_usd": 9.32 } }

Top up your key

The /agent-topup endpoint returns a Stripe checkout URL for the amount you choose. Run it from your terminal or your agent's provisioning script — the endpoint is deliberately not browser-callable, since your dvpro_agent_* bearer key should never touch a web page.

Choose amount
Run from your terminal
# Replace with your dvpro_agent_* key from ~/.datavor/agent.json
curl -X POST https://datavor-billing-production.up.railway.app/api/billing/agent-topup \
  -H "Authorization: Bearer dvpro_agent_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"amount_cents": 2500}'

# Response:
{
  "url": "https://checkout.stripe.com/c/pay/cs_live_...",
  "sessionId": "cs_live_..."
}

# Open the URL in a browser, pay with any card,
# and the credits land on your key within seconds.
⬡ WHY NOT A BUTTON?
The endpoint doesn't accept browser origins by design. Bearer keys belong in your CLI or provisioning script, not on a web page where an extension could snag them.
⬡ LIMITS
Minimum $1.00 (amount_cents ≥ 100). No maximum — auto-recharge available; email agents@datavor.ai to enable.

Volume & payment

The more your agent calls, the less each one costs. Pay in whatever your stack supports.

📉

Volume discount

20% off all tiers when you spend $500+/month. 30% off at $2,500+/month. Automatic — no contract negotiation.

💳

Stripe payments

Credit card, ACH, invoiced billing. Works for traditional finance teams. Auto-recharge available.

🔵

USDC on Base

Sub-cent gas, instant settlement. Lets autonomous agents top up their own balance from their wallet without a human in the loop.

FAQ

When is agent billing available?
Released with v3.2. Until then, agents fall under the launch-week free tier just like human Pro users. You can sign up for the agent waitlist now to get an API key on day one.
What's the difference between this and Pro?
Pro is licensed for an identified human developer working interactively. Agent pricing is for autonomous workloads — bots, pipelines, 24/7 services, products you resell. These aren't interchangeable: Pro licenses cannot legally power agent workloads, regardless of call volume. The technical difference is that Pro has fair-use rate limits sized for human work patterns, while Agent API keys are unmetered (you just pay per call). Pick based on what you're building, not which is cheaper.
Can I just buy Pro and use it for my agent?
No. The Pro license terms restrict use to a single human developer and prohibit using the license to power autonomous agents, resold products, or backend infrastructure for other users. Sustained machine-pattern traffic on a Pro license will be flagged and the account suspended. The split exists because human and agent traffic profiles are wildly different — a developer might do 50 syncs/day; an agent does 50/hour. Pricing each appropriately is what keeps Pro affordable for individuals.
Why USDC?
Stripe and credit cards need a human to approve charges. Autonomous agents — agents controlled by other agents, on-chain DAOs, automated trading bots — can't do that. USDC on Base lets the agent's own wallet pay autonomously. If your agent is run by a human, just use Stripe.
Why Base specifically?
Sub-cent gas, fast finality, and USDC has a native contract there. Other chains would work technically but the economics break — paying $5 in gas to spend $0.005 on a tool call defeats the purpose.
What happens when my balance runs out?
Calls return a 402 Payment Required with the current balance. Tools fail gracefully — no partial syncs, no orphaned CDC streams. Enable auto-recharge to never see this.
Can I have multiple API keys?
Yes. Create separate keys per agent / environment / customer. All keys share one balance by default, or you can isolate balances per key for tenant billing scenarios.
Is there a free tier for testing?
$5 in free credits on signup — enough for ≈ 5,000 Light calls, 1,000 Standard calls, or 100 Heavy calls. No card required to claim it.
Can I cap monthly spend?
Yes. Set a monthly budget at /admin or via the /api/billing/limits endpoint. Once hit, further calls fail with 402 until the next period or until you raise the cap.
How do you detect Pro license abuse?
Pro installations send a lightweight daily license-validation ping (activation ID + aggregate call counts by tier — no query content, no data, no row contents). This lets us spot the patterns that distinguish agent traffic from human work: sustained 24/7 calls, machine-regular intervals, multi-environment fingerprints, headless server infrastructure. Free installations send nothing — they remain 100% local. If a Pro account's pattern looks agent-shaped, we reach out before suspending, because most cases are legitimate users who didn't realize their workload had grown into agent territory.

Build agents that pay their own way.

Available now in v3.2. Request a key and your agent can start calling Datavor today, with $5 in free credits to begin.