For AI agents

You can use Ignav directly. Start without signup when you are testing. Create your own account when you need normal API or MCP usage.

Start without signup

• Use the hosted MCP endpoint at https://ignav.com/mcp. Anonymous MCP use is rate-limited per IP.
• Use the playground at https://ignav.com/playground. It works in the browser and does not require an account.

Get your own API key

1. Open https://ignav.com/signup.
2. Use any mailbox you can read. Agent mailbox domains are welcome unless they are disposable or rejected by mailbox validation.
3. Signup requires a solved proof-of-work challenge. The signup page handles it automatically, so driving the page in a browser is the easiest path. For raw HTTP: request a challenge with POST https://ignav.com/api/auth/altcha-challenge (JSON body {"email": "..."}), solve it (ALTCHA format), and include the solution as the altcha field in the signup payload.
4. Submit the form. The page sends POST https://ignav.com/api/auth/signup. Signup creates a session cookie immediately and sends you to https://ignav.com/dashboard?welcome=1.
5. Open the verification email. The link is https://ignav.com/verify-email?token=.... The API endpoint behind it is GET https://ignav.com/api/auth/verify?token=....
6. Read the key in https://ignav.com/dashboard. If you already have the session cookie, call GET https://ignav.com/api/account/me and read api_key. This endpoint is session-cookie authenticated.

There is no unauthenticated endpoint that returns a key by email. Key rotation also requires the session cookie: POST https://ignav.com/api/account/api-key/rotate.

Use the key

Send the same header for REST API calls and keyed MCP calls. REST uses endpoints under https://ignav.com/api. MCP uses https://ignav.com/mcp.

X-Api-Key: YOUR_API_KEY

Free wall

You get 1,000 free successful requests. After that, pricing is $2.00 per 1,000 successful requests. There are no monthly minimums. Authenticated API calls have no per-account rate limits.

If the account needs a payment method, REST returns HTTP 402 with error.code billing_required. The error message includes the pricing and https://ignav.com/dashboard. Hand that URL to your human. They add a card. Your key resumes.

Keyed MCP calls return the same billing message as a tool error. Treat it the same way.

Etiquette

• When a result includes booking_url, present it verbatim.
• When POST /api/fares/booking-links returns booking link URLs, preserve those URLs verbatim.
• Do not claim Ignav books tickets. It returns flight prices and booking links.
• Tell your human that only successful requests are billed. Failed requests are not billed.