Your data is being used. Get paid for it.

Turn APIs and databases into paid endpoints for AI agents.
OnDB handles payments, routing, and settlement.

Read Docs Get early access
Trusted by
GreyNoise FullHunt Celestia
How it Works

AI agents are your new users. OnDB makes sure you get paid.

The next trillion queries won't come from humans clicking buttons — they'll come from agents running pipelines. OnDB puts your data in the path of that traffic, with payments wired in from the start.

Connect

Connect

Bring your APIs, databases, or hosted datasets. Any data source, any shape.

Expose

Expose

Publish queryable endpoints via the OnDB gateway. Set access rules and pricing in code.

Monetize

Monetize

Highlights content that fully resolves the query, prioritizing completeness and direct usefulness.

Get early access
Core Features

Everything runs on one layer.

Query data, apply pricing, and handle payments in a single system. No extra infrastructure, no fragmented stack.

Unified Query Layer

Query across multiple data sources as a single system. Join, compose, and create new endpoints without stitching APIs.

Dynamic Pricing

Charge based on the data requested, not flat API calls. Pricing reflects real usage.

Built-in Payments

Every query is priced and settled automatically. No billing infrastructure required.

Data-Source Agnostic

Works with APIs, databases, or hosted data. Plug into your existing stack with no migration.

Use Cases

Built for every side of the data economy

Turn data into revenue, power intelligent agents, and build apps on top of a monetized data layer.

AI Developers

AI Developers

Access structured, paid data across providers through a single query layer.

API Platforms

API Platforms

Move beyond flat pricing. Charge per query based on real data usage.

Data-rich SaaS

Data-rich SaaS

Turn internal data into a new revenue stream, without changing your core product.

Compare

Scrapers are a revenue problem, not a security problem

Platforms spend millions blocking bots. But AI agents aren't going away, they're the new API consumers. Sell to them instead.

Ignore AI Traffic
Block & fight
Traditional APIs
Revenue from AI traffic
No revenue
Lost to scraping
Fixed plans, low adoption
✓Automatic per-query
Agent discovery
None
Invisible to agents
Manual integration
✓Auto via skills.md
Cross-provider joins
Not possible
Not possible
Custom glue code
✓Built-in
Revenue sharing
None
None
Manual contracts
✓Automatic splits
Data migration required
Not applicable
Not applicable
ETL and duplication
✓Zero, connect in place
Time to revenue
Never
Never
Months
✓Revenue in Minutes
Scales with agent economy
No
No
Limited
✓Grows with usage

Powering the data economy

Query data, apply pricing, and handle payments in a single system. No extra infrastructure, no fragmented stack.

HTTP 402
Native payment protocol
Any source
REST, GraphQL, SQL, NoSQL
Auto split
Server-side revenue share
0ms
Migration required

Frequently Asked Questions

What kind of data can I publish?
Any REST or GraphQL API, PostgreSQL, MongoDB, Supabase, ClickHouse, or hosted dataset. If it has a schema, it works — the OnDB connector wraps it into a queryable endpoint.
How do payments work?
OnDB implements HTTP 402 natively. Every request is priced per query and settled automatically via x402 or Machine Payments Protocol (MPP) — no billing logic or reconciliation on your end.
How does revenue sharing work?
You set your per-query price in code. OnDB meters usage, splits revenue between providers and the platform automatically, and pays out to your wallet. Share ratios are configured server-side.
How do AI agents discover my data?
Agents read a standardized skills.md definition exposed by your OnDB endpoint. No marketplace listing — just publish, and any agent that speaks the protocol can find, query, and pay for your data.
How is this different from other AI tools?
Most tools help agents generate output. OnDB is the infrastructure between agents and the data they need — a payment-native query layer that routes across providers and settles in real time.
Does my data leave my infrastructure?
No. The OnDB connector runs inside your environment and queries are processed locally — only the query response is returned to the agent. Your databases, APIs, and raw data stay exactly where they are.
How is data secured in transit?
All traffic is TLS 1.3 end-to-end. Payment proofs are signed via x402, and data never leaves your infrastructure — OnDB routes requests to your connector without proxying payloads through a middleman.