Describe the API call. AI builds and tests it.
Free for 7 days, no credit card required
Say what the step should do in your own words. It finds the service, reads its docs, helps you get a key, tests the request for real and fills the HTTP step in.
- Meta's official API, no password, nothing installed
- Unlimited contacts on every plan
- AI replies in your customer's language
- From $29 a month
From a sentence to a tested request
The same four moments every time, each shown in the chat as it happens.
- 01
Say what it should do
In your own words, as you would tell a friend. Paste the service’s link or its docs if you have them; a screenshot works too.
Or start from three examples in the panel
- 02
It finds and reads
It searches for the service’s official docs, reads the page, and reads your screenshot word for word, each shown as a line as it happens.
You can stop it at any moment
- 03
It tests it for real
Every setup ends in a real call. A passing test shows the first values that came back; a failing one is read and fixed.
The same test as Send test request
- 04
You pick what to use
Pick the values you need with one click each, and the step is filled in, wired with Success and Failed, ready to save.
Nothing goes live until you save the flow
Everything it handles, in the panel’s words
The labels you will see in the chat, what each one does, and the rule behind it.
The conversation
A chat in the step’s own panel, saved with the step.
- Set it up with AIDescribe it, it builds it
Say what you want in your own words. It finds the service, helps you get a key and tests it for you, then fills in the method, address, parameters, headers, auth, body and which values to use.
- Attach a screenshotScreenshots, read word for word
A screenshot of the API’s docs or of the service’s dashboard is read as text, so a key’s name, a parameter or an example answer is never guessed.
PNG, JPG or WebP; up to four with one message.
- Ask before switchingThree ways to work
Ask before switching checks with you before using a different service than the one you named. Auto picks the service and settings itself. Bypass permissions never stops to ask and says what it assumed.
In every mode, your API key is yours to add, and it is only ever sent to its own service.
- Saved with this step.Pick it up days later
The chat stays with its step, so you can come back, ask a question about the request or change it, and it carries on from the step as it is now.
- From Build with AIStarted by Build with AI
When Build with AI places an HTTP step it cannot finish without you, it leaves the goal in your words, and Set it up with AI starts from it.
Your key
The one thing the AI never touches.
- Your API keyThe key box
When a service needs a key, the chat shows a hidden key box. The key goes straight into the step, locked, and the AI only learns that a key is set.
Stored encrypted on this step. The AI never sees it.
- That looks like a key.A key in the chat is stopped
A key pasted into the message is caught before it is sent: “Keys never go in the chat: paste it in the key box below, which puts it straight into the step, locked.”
- Tested itA refused key is never retried blindly
When a service turns a key down, the AI says so and asks for a new one in the key box instead of trying the same key again.
What it reaches for first
Free services it already knows work.
- Ready servicesTwelve tested services first
For rates, weather, holidays, postcodes, Wikipedia, time zones and more it starts from the ready services: free, no key, commercial use allowed, each tested daily with a real request.
Each service’s documented limits travel with it, so the AI can tell you them.
- Any APIOr any API you name
Your shop’s API, your CRM, your booking system: point it at the docs and give it a key in the key box.
Auth is a token, a key or Basic; there is no “connect your account” sign-in for other apps.
The AI never sees your key
Keys go in a locked box that writes straight into the step. Paste one into the chat by mistake and it is stopped before it is sent.
- The key box
- Shown when the service needs a key; the AI only learns that one is set.
- Sealed
- Encrypted with AES-256-GCM, bound to your account, opened only on our server.
here is my key fx_9c1e44b2a7…
That looks like a key. Keys never go in the chat: paste it in the key box below, which puts it straight into the step, locked.
Your API key
••••••••••••••••Add key
The key goes straight into this step, locked. The AI never sees it.Stored encrypted on this step. The AI never sees it.
Show it the docs, it reads them
Attach a screenshot of the API’s docs or your dashboard and it reads it word for word, then tests what it read.
- Attach a screenshot
- Up to four with one message: PNG, JPG or WebP.
- Read your screenshot
- Each picture shows as a line in the chat, like a page it read.
Latest ratesGET /v1/latest
| from | Base currency, e.g. USD |
|---|---|
| to | Target currencies, comma separated |
| amount | Amount to convert, default 1 |
Convert our bag prices to the currency they ask for
Read your screenshot
Tested it: 200rates.EUR21.297
Paid in AI credits, by what it does
Most setups take a few answers, a search and a page read.
| What | AI credits |
|---|---|
| An answer from the AI | About 1 AI credit |
| Each page it reads or search it runs | 1 AI credit |
| A closer look by a stronger model | 3 AI credits |
| Each screenshot it reads | 2 AI credits |
| A call that failed on our side | Nothing |
| Messages a day | A trial: 60. A paid plan: no daily limit |
| Screenshots per message | Up to 4: PNG, JPG or WebP |
| Plan | Starter and up, with the flow builder |
From the app’s AI credit table. AI credits come with every plan, equal to its monthly comment pool; a trial has 250.
Questions about the AI builder
What people ask before they let it set up a request.
No. Describe the job the way you would to a friend, like “send each new lead’s name and email to my CRM”. It picks the method, the address, the parameters and the auth, and asks you only for what it cannot find, such as your key. Build with AI builds whole flows; this builds one request inside one.
It is Set it up with AI, a chat inside the HTTP request step. You say what the step should do in your own words, and it finds a service, reads its docs, helps you get a key, tests the request for real and fills the step in: method, address, parameters, headers, auth, body and the values to use.
No. When a service needs a key, the chat shows a hidden key box; the key goes straight into the step, sealed with AES-256-GCM, and the AI only learns that a key is set. A key pasted into the chat itself is stopped before it is sent.
About 1 AI credit per answer, plus 1 for each page it reads or search it runs, 3 when a stronger model takes a closer look, and 2 for each screenshot it reads. A call that fails on our side costs nothing. AI credits come with every plan, equal to its monthly comment pool.
Yes. Attach up to four screenshots (PNG, JPG or WebP) with a message and it reads them word for word, so a parameter name or an example answer is taken from the picture, not guessed.
Any API with a documented request: your own shop or booking system, a CRM, or a public service. For common jobs (exchange rates, weather, public holidays, postcodes, Wikipedia, time zones) it starts from twelve free services that are tested every day.
Yes, every setup ends in a real call from our server, and the chat shows each test as a line with the first values that came back. A failing test is read and fixed; nothing goes live until you save the flow.
Yes. The work streams live and can be stopped at any moment. The chat stays with its step, so you can come back days later and change the request or ask why it was set up that way.