Your queries, callable from outside — simply and safely.
Save a query you use often and it gets its own address. Other programs just call that address to get the results. Every call is permission-checked and kept on record.
Run specific queries from outside — simply and safely
A saved query gets a callable address, and outside programs just call it. Get the results in whatever shape you want — JSON · CSV · XML · table (HTML) — and every call is permission-checked and recorded.
Save a query,
get an API.
When you save a query, you pick its address (e.g. /api/user) — and that address becomes a callable API. No extra code to write: other programs call the address and get the results back.
Call with conditions,
answer in any format.
Attach what you're looking for (say, a customer group) to the address, and the query runs with those conditions. Get results as JSON · CSV · XML · table (HTML). For queries that change data, it tells you how many rows were affected.
API calls,
reliably recorded.
Every API call is recorded too — who, from where (IP), which SQL, and when — kept right alongside your editor · MCP · CLI activity on one screen.
For teams building on top of your databases
Same way for every database
MySQL, PostgreSQL, Oracle, SQL Server and more — the save-and-call flow is the same for every database. Programs only need to call an address.
Four response formats
Get results as JSON · CSV · XML · table (HTML) — whichever you prefer. Without a choice, results come back as JSON.
Masking + automatic value conversion
The same masking rules apply to API responses, so sensitive data stays hidden. Values passed in the address are auto-converted to the right type — numbers, dates, and so on.
One query becomes an API — called safely
Teams use TadpoleHub API Hub to open up database access the same safe way across services and environments.