Quickstart
Account, service, key, one environment variable, agent. Five minutes, one secret in your repository.
Five minutes from a blank project to a real service call, with one secret in your repository. This is the whole setup.
The five steps
Create your Squiid account
Sign up, pick Solo or Team, and add credits. Credits are prepaid and denominated in USD. $1 of credit is $1 of provider usage.
Add a service
Open the catalogue and click add on the service you need, for example Supabase. Squiid provisions the upstream project and keeps the provider credential.
Copy your key
Your key looks like sq_live_…. One key reaches every service you have added. Create a second key per project if you want separate audit trails.
Put it in .env
Add SQUIID_API_KEY=sq_live_… to your project .env and remove any provider keys you were carrying.
Point your agent at the gateway
Tell your agent that all calls go to https://api.squiid.io/v1/<service>/ with Authorization: Bearer $SQUIID_API_KEY, then check usage in the dashboard.
1. Create an account and add credits
Sign up at squiid.io/signup and choose a plan. The free plan is $0 a month with a 15% fee on credit top-ups and a $50 minimum top-up. Solo is $19.97 a month and its top-up fee starts at 8%, falling as your spend grows. Team is $29.97 per seat per month for the first five seats, less above that, one point lower on the fee ladder. Credits are prepaid in USD and spend at par: no markup is added to what the provider charges.
2. Add a service
Open the catalogue, find the service, click add. For provisioned services Squiid creates the upstream project. For connect services such as Stripe or GitHub you authorise the account you already have. Either way, Squiid ends up holding the credential and you never copy it.
3. Copy your key
Keys look like sq_live_…. One key reaches every service on your account. Create separate keys per project or per agent if you want to see which made which call, or to revoke one without touching the others.
4. One line in .env
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxThen every call your app or your agent makes goes to the gateway with that one key:
curl https://api.squiid.io/v1/supabase/... \
-H "Authorization: Bearer $SQUIID_API_KEY"Delete every provider key you were carrying. If your deploy target has its own environment settings, add the same single variable there.
5. Point your agent at the gateway
Most SDKs take a base URL:
// Supabase
import { createClient } from '@supabase/supabase-js';
const db = createClient('https://api.squiid.io/v1/supabase', process.env.SQUIID_API_KEY);
// OpenAI
import OpenAI from 'openai';
const ai = new OpenAI({
baseURL: 'https://api.squiid.io/v1/openai',
apiKey: process.env.SQUIID_API_KEY,
});
// Resend, plain fetch
await fetch('https://api.squiid.io/v1/resend/emails', {
method: 'POST',
headers: {
Authorization: 'Bearer ' + process.env.SQUIID_API_KEY,
'Content-Type': 'application/json',
},
body: JSON.stringify({ from: 'hi@yourdomain.com', to: 'you@example.com', subject: 'It works', html: '<p>Hello</p>' }),
});Then put the convention in your agent rules file, so you never have to repeat it:
# Services
All third-party calls go through the Squiid gateway.
Base URL: https://api.squiid.io/v1/<service>/
Header: Authorization: Bearer $SQUIID_API_KEY
Never add provider-specific API keys to this repo.That block works in CLAUDE.md, AGENTS.md, .cursor/rules, .windsurf/rules/, .clinerules, GEMINI.md and .github/copilot-instructions.md. Per-agent notes are on the agent pages.
6. Check the dashboard
Make one call and open the dashboard. You will see the call against the service, the key that made it, and the credit it drew down. Set an auto top-up threshold and a monthly cap while you are there. See spend controls.
Questions people ask
How long does the first integration take?
About five minutes for a service that is instant access, longer for anything that needs domain verification such as email, where DNS records take time to propagate. The Squiid side is a click; the provider side is whatever that provider normally requires.
Do I need to change my SDK?
No, just its base URL. Every major SDK exposes a base URL or endpoint option, so the change is one line at the point where you construct the client. Raw fetch calls change their URL and their header and nothing else.
Can I have more than one key?
Yes. Create a key per project or per agent so the dashboard shows which one made which call, and so revoking one does not affect the others. All keys draw on the same credit balance unless you set per-key limits.
How do I check that it worked?
Make one call, then open the dashboard. Usage appears against the service with the key that made it. If a call fails, the gateway returns a normal HTTP status with a message saying whether the problem is the key, the service, or the credit balance.
What should I do first after the quickstart?
Set an auto top-up cap so a runaway agent cannot drain your balance, then read the gateway convention so your agent rules file says the right thing. After that, add the rest of the services this project needs.
Five minutes to one key.
Add the services your project needs and give your agent a single credential.