PerSQL for developers
PerSQL keeps a person’s own SQLite databases: one database per thing you keep track of, tables you can query, files you can import and export, backups you can restore. The console and the phone are for anyone. These pages are for the person who would rather reach the same databases from code.
Three doors open onto the same account:
- HTTP — every route the console uses, on
https://api.persql.com, with a developer key as a bearer token. Reference → - MCP — the same databases served to an agent as tools: list, describe, sample, query, note, back up. Over HTTP, or over stdio through the CLI. Set it up →
- CLI —
persqlin a terminal: query, import, export, back up and restore, and serve MCP. Commands →
A database is as large as the platform allows — ten gigabytes, rows in the millions — and every byte that moves is a job you can watch. How data comes and goes →
Start by making a key on the console’s Account page, then follow Getting started.