Skip to content
Sign in
Menu

Test an API before launch

Use test calls to confirm your API answers billably before agents can call it.

  • Tutorial
On this page

What you'll achieve

Confidence that the paths agents will call return billable answers in time.

Prerequisites

  • A draft API with its upstream URL and key saved.

1. Test a real path

Run a test on the path agents are most likely to call, with realistic parameters.

2. Check the timing

The panel shows how long your API took. Test calls wait 10 seconds; paid calls wait 20. Endpoints that are close to either limit will fail some paid calls.

3. Check the content

Read the response preview. Make sure the answer is the data an agent paid for, not an error wrapped in a 200.

4. Test the bodies you expect

For POST, PUT or PATCH paths, add a JSON body like the one callers will send.

Expected result

Test passed. Agents would be charged for this answer. The Launch step unlocks.

Common mistakes

MistakeFix
Testing / on an API whose root returns nothingTest a data path; an empty answer doesn't meet the default billing rule.
Relying on a redirectRedirects aren't followed. Use the final URL as the upstream base.
Changing the key after testingA key change resets the test. Run it again.