# OINO.cloud > OINO.cloud turns a SQL database you own (PostgreSQL, MySQL, MariaDB, SQL Server) into secure REST APIs and an MCP server that AI agents can use directly: inspect and change the schema, read and write data through tokens, and publish HTML pages and authenticated apps, with access controlled by roles, OAuth or enterprise SSO. The data stays in your database; OINO.cloud stores only the configuration. There is a free plan, and AI agents can start the signup for their user through a JSON API. ## Signing up as an agent An agent can request a free account for its user, either through the public onboarding MCP server or the plain JSON API below; both work the same way. Onboarding MCP server (streamable HTTP, no authentication): `https://account.oino.cloud/onboarding/mcp`, also listed in the MCP Registry as `cloud.oino/onboarding`. Tools: `describe_service`, `list_plans`, `signup` (email, optional name) and `signup_status` (signupToken). JSON API: A human always confirms it: the account is created only when the user opens the confirmation link emailed to them, so make sure the email address is the user's own and that they agree to sign up. 1. `POST https://account.oino.cloud/signups/v1` with JSON `{"email": "user@example.com", "name": "Customer or company name"}` (`name` is optional). The response is `202` with `{"status": "pending", "signupToken": "...", "expiresAt": "...", "message": "..."}`. Keep the `signupToken` secret; it only lets you read the status of this signup. 2. Ask the user to open the link in the email "Confirm your OINO.cloud signup" and press "Confirm and sign in". This creates the account on the Free plan and signs them in. 3. Poll `GET https://account.oino.cloud/signups/v1/{signupToken}` (no more than once every 10 seconds). It returns `{"status": "pending"}` until the link is used, then `{"status": "active", "customerId": "...", "links": {"account": "...", "billing": "..."}}`. `404` with `{"status": "expired"}` means the signup expired (after 7 days) or the token is unknown. The response is the same whether or not the email already has an account. An existing user gets a normal sign-in link instead, and the status stays `pending`. Errors: `400` (invalid email, emails over 50 characters, disposable email domains), `429` (too many attempts, see `Retry-After`). The `links` require the user to be signed in to OINO.cloud: `account` opens their account, and `billing` opens the plan selection or the subscription management. Payments always happen in the browser of the user, never through the API. ## Connecting an agent to the user's database After signup, guide the user through the account app (https://account.oino.cloud): 1. Databases: add their database connection (host, port, database, user, password). 2. MCP Servers: create an MCP server bound to that one database. Turn on "Allow Schema Manage" if you should change the schema and publish pages and apps, and "Allow Data Manage" if you should write data. 3. Give the MCP server's connection URL and bearer token to you (the agent) as an MCP server configuration. MCP servers can also use OAuth login when the server allows auth roles. Through the MCP server you can then list and create tables, provision the REST data APIs and tokens, read and write data, publish pages and apps, define roles and read the subscription's recent logs. ## Plans - Free: EUR 0 / month, 2 GB traffic, 1 MCP server, 2 releases of history. - Pilot: EUR 50 / month, 10 MCP servers included (+EUR 1.50 / server / day), 10 GB traffic included (+EUR 1.20 / GB), 10 releases of history. - Production: EUR 160 / month, 100 MCP servers included (+EUR 1.50 / server / day), 100 GB traffic included (+EUR 1.20 / GB), 100 releases of history. When the data quota is used up, the account is disabled for the rest of the day. Billing is handled by Polar as the merchant of record. ## Docs - [Getting started for AI agents](https://oino.cloud/guides_agents.html): the signup and connection flow above, for humans and agents - [AI Apps: MCP server](https://oino.cloud/guides_aiapps_mcpserver.html): creating an MCP server and what an agent can do with it - [AI Apps: roles](https://oino.cloud/guides_aiapps_roles.html), [pages](https://oino.cloud/guides_aiapps_pages.html), [apps](https://oino.cloud/guides_aiapps_apps.html) - [Setup](https://oino.cloud/guides_setup.html): databases, APIs, tokens, templates and security - [SQL parameters](https://oino.cloud/guides_sqlparams.html): filtering, ordering, limits and aggregation in the REST APIs - [Migrations](https://oino.cloud/guides_migrations.html): characterizing a legacy application's database behavior to rewrite it with generated tests - [FAQ](https://oino.cloud/faq.html) - [Privacy and GDPR](https://account.oino.cloud/gdpr) ## Optional - [Legacy migration skill](https://oino.cloud/skills/legacy-migration/oino-legacy-migration.md): an agent skill for the migration workflow - [Sign up in a browser](https://oino.cloud/signup.html) - [Personal Agent Protocol discovery document](https://oino.cloud/.well-known/poppy.json): lists the onboarding MCP server