Quick start
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. Every request is authenticated with your Squiid key, the base URL is https://api.squiid.io/v1, and the cost comes back on every response.
The first call
export SQUIID_API_KEY=sq_live_…
curl https://api.squiid.io/v1/ai/chat/completions \
-H "Authorization: Bearer $SQUIID_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"anthropic/claude-sonnet-5","messages":[{"role":"user","content":"hi"}]}'import OpenAI from "openai";
const ai = new OpenAI({
baseURL: "https://api.squiid.io/v1/ai",
apiKey: process.env.SQUIID_API_KEY,
});
const res = await ai.chat.completions.create({
model: "anthropic/claude-sonnet-5",
messages: [{ role: "user", content: "hi" }],
});from openai import OpenAI
ai = OpenAI(
base_url="https://api.squiid.io/v1/ai",
api_key=os.environ["SQUIID_API_KEY"],
)
res = ai.chat.completions.create(
model="anthropic/claude-sonnet-5",
messages=[{"role": "user", "content": "hi"}],
)The five steps
Create your Squiid account
Sign up (Free is fine to start), add credits, and pick Solo or Team when you want port-ins and lower fees. Credits are prepaid and denominated in USD. $1 of credit is $1 of provider usage.
Add a service
Open the catalog 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 console.
1. Create an account and add credits
Sign up at squiid.io/signup and choose a plan. Free is $0 a month with a 15% fee on credit top-ups and a $50 minimum top-up, and it carries unlimited projects, one key, budgets and spend caps: it is a real plan to start on, not a trial. Solo is $19.97 a month, its top-up fee starts at 8% and falls to 3.5% as monthly spend grows, and it adds port-ins. Team is $29.97 per seat per month for the first five seats, less above that, with a fee that starts at 7% and falls to 3%. Custom exists above $10k a month or 20 seats. Whichever you pick, credits are prepaid in USD and spend at par: no markup is added to what the provider charges. The current numbers are always on the pricing section.
2. Add a service
Open the catalog, 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_xxxxxxxxxxxxxxxxxxxxDelete 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, and agent setup covers the endpoint that writes the block for you.
6. Check the console
Make one call and open the console at app.squiid.io. 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 console 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 console. Usage appears against the service with the key that made it, and x-sq-request-id on the response is the same id the ledger shows. If a call fails, the gateway returns a normal HTTP status saying whether the problem is the key, the service, or the 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.