Custom APIs
The Custom APIs plugin lets the AI connect your site to outside services — live weather, shipping quotes, market prices, a spreadsheet-replacement your company runs, any service with an internet API. You describe the integration (or just paste the service's documentation); the AI does the wiring.
What you can build with it
"Connect the OpenWeather API and show a 5-day forecast for the visitor's city."
"Here are our logistics provider's API docs (attached) — quote shipping at checkout."
"Pull live prices from this market-data API and refresh them every minute."
How it works
- Describe the integration in chat. Name a well-known service, paste docs, or attach a PDF/ZIP of them. The AI turns that into a connection — a reviewed description of the service: its address, how it authenticates, and the exact operations your site may call. No code from the docs ever runs; the AI only reads them.
- The AI writes the glue. Small server-side functions call the connection's operations (for example, asking three shipping providers for quotes in parallel) and hand clean results to your pages.
- Add credentials when you're ready. Each connected service appears as a card in your project's Connections section on the dashboard. A service that needs an API key shows Waiting for credentials — your site keeps working against realistic sample data until you paste the key in, then switches to the live service.
That last point is worth using deliberately: you can build and polish the whole feature before signing up for the external service.
Turning it on
On your project's page, switch the Custom APIs card on. There's nothing to configure up front — credentials are entered per-service, on each connection's card, as integrations appear.
The safety model
External services and credentials are exactly where things could go wrong, so the guardrails here are strict and not up to the AI:
- Credentials are write-only and never visible to the AI, the chat, or the functions themselves — a trusted intermediary attaches them to outgoing calls.
- Only declared operations can be called. A function can't invent new URLs or quietly send your data somewhere you haven't approved.
- Anything consequential asks first. Operations that spend money or change something important always confirm with the visitor through a trusted dialog — and you approve such functions once, on your admin panel, before they can run at all.
- Everything is inspectable: your admin panel's Connections and Functions pages show what exists, what's enabled, and recent activity.