Getting a key

Formsieve uses your own Jev API key: you are the provider's customer, usage is billed to your account, and Formsieve (and Thinking42) never sees your key or your form data. Jev is TypeSafe AI, Inc.'s decision model; you can reach it directly or through a gateway that resells access.

Last checked: 2026-09-22. Signup status, prices and terms below were read on that date and can change at any time, especially while Jev is in early access. Check the provider's page before you buy.

Which route should I choose?

Our recommendation for the most stable behaviour: TypeSafe direct if you already have an account, otherwise OpenRouter. Vercel works well, but it does not tell Formsieve which Jev version answered (see Calibration).

One key may be used on all of your own sites. Do not create several accounts with one provider to collect extra promotional credit: TypeSafe's customer agreement (section 8.2(b)) forbids it and names it as grounds for suspension.

TypeSafe (direct)

As of 2026-09-22, TypeSafe has temporarily paused new signups (announced on 2026-09-22 at 06:19 UTC; new visitors to the console see "Whoops, we're full"). No reopening date has been announced. Existing accounts keep working.

If you have an account:

1. Sign in at https://console.typesafe.ai and create an API key (https://console.typesafe.ai/keys).
2. Make sure the account has credit. TypeSafe bills prepaid credit ("Customer must obtain TypeSafe-managed credits", Master Customer Agreement section 8.2); purchased credit expires after 12 months at most, and without auto-refill TypeSafe may decline requests when credit runs out.
3. In Formsieve choose TypeSafe (direct) and paste the key.

Price: $0.042 per million input tokens, output free (as of 2026-09-22). This route pins exactly jev-1.13.0, the version Formsieve's thresholds were set for.

Terms: https://typesafe.ai/legal/mca · Privacy: https://typesafe.ai/legal/privacy-policy · DPA: https://typesafe.ai/legal/data-processing

Vercel AI Gateway

Open for signups as of 2026-09-22. No TypeSafe account is needed.

1. Use a Vercel team on a paid Pro or Enterprise plan. Vercel's Hobby plan is for personal, non-commercial use only, has no data processing agreement, and Vercel's terms allow it to use Hobby and trial content for model training. A business website should not use it.
2. Add a valid payment method to the team. Vercel requires one even for free credits; without it, calls fail with customer_verification_required, which Formsieve reports as "add a payment method".
3. In the Vercel dashboard, create an AI Gateway API key for that team (Vercel's guide for Jev: https://vercel.com/docs/ai-gateway/sdks-and-apis/typesafe).
4. In Formsieve choose Vercel AI Gateway, paste the key and tick "My Vercel team is on a paid Pro or Enterprise plan".

Price (as of 2026-09-22): TypeSafe's list price of $0.042 per million input tokens (output free) with no markup; payment-processing fees are yours. Purchased credits expire one year after purchase.

Good to know:

• Vercel serves Jev as typesafe-ai/jev and does not report which Jev version answered. Formsieve shows the route as "Version not reported". See Calibration.
• For a contractual zero-data-retention switch you can enable team-wide ZDR in Vercel (Pro and Enterprise; $0.10 per 1,000 requests as of 2026-09-22). Vercel already routes Jev only to TypeSafe under a zero-data-retention agreement.
• Do not add a TypeSafe key inside Vercel ("bring your own key" there) unless you hold a zero-data-retention contract with TypeSafe; with such a key, TypeSafe's standard terms apply instead.
• Vercel's AI Product Terms ask you to tell visitors in advance that your site uses AI. Formsieve's "screened by an automated AI service" line under the form is therefore on by default for this route (Privacy kit).

OpenRouter

Open for signups as of 2026-09-22. No TypeSafe account is needed: OpenRouter bills Jev to your OpenRouter credit.

1. Create an account at https://openrouter.ai and buy credits. OpenRouter requires prepaid credits for API calls: minimum $5 per purchase, plus a 5.5% fee ($0.80 minimum), so $5 of credit costs $5.80. There is no free Jev variant. Unused credit may expire 365 days after purchase, and refunds are possible only within 24 hours.
2. Create a key at https://openrouter.ai/settings/keys. You can give the key its own credit limit.
3. In your OpenRouter privacy settings keep input and output logging and "OpenRouter use of inputs" off.
4. In Formsieve choose OpenRouter and paste the key. Leave Require zero data retention on: Formsieve then asks OpenRouter to use only zero-data-retention endpoints that do not collect data (provider.zdr and provider.data_collection: deny on every request). If none is available, the submission is not checked and follows your fail mode, and a notice tells you (Troubleshooting). Switching the setting off asks for consent again, because the data policy of the route changes.

Price: $0.042 per million input tokens with no inference markup (as of 2026-09-22); $5 of credit covers roughly 80,000 to 110,000 checks at 1,100–1,500 input tokens each. OpenRouter serves typesafe/jev-1.13 and reports the snapshot that answered (typesafe/jev-1.13-20260917 as of 2026-09-22), which Formsieve recognises as calibrated.

Terms: https://openrouter.ai/terms · Privacy: https://openrouter.ai/privacy · DPA: https://openrouter.ai/data-processing-agreement

Custom base URL

For a proxy you operate or trust, for example a LiteLLM pass-through that forwards to TypeSafe with your own TypeSafe key (this pins jev-1.13.0 exactly).

1. In Formsieve choose Custom base URL.
2. Enter the base URL (HTTPS; plain HTTP is accepted only for localhost, 127.0.0.1, ::1 and *.test hosts), the path (default /v1/systemone) and the model (default jev-1.13.0).
3. Paste the key your proxy expects and confirm that you have your own agreement with the proxy operator.

On multisite, a key defined in wp-config.php (or supplied by a filter) covers the whole network and is not sent to a Custom base URL entered by one site's administrator: saving such a route is refused, a route saved earlier shows an error notice, and its submissions are logged as "no API key". Set the base URL network-wide as well, with the FSV_GF_API_BASE constant or the fsv_gf_api_base filter (Gravity Forms) or FSV_CF7_API_BASE constant or the fsv_cf7_api_base filter (Contact Form 7).

AI/ML API. Formsieve recognises api.aimlapi.com and uses its /v1/decisions path and typesafe/jev model. As of 2026-09-22 it is prepaid (free tier paused, no refunds) at $0.0577668 per million input tokens. Formsieve shows this warning for it: "This provider publishes no Data Processing Agreement and no statement on retention or training of API inputs; you are responsible for having a lawful basis and contract." It is not one of the presets for that reason.

As of 2026-09-22, AI/ML API's published request schema accepts only plain-text criteria, while Formsieve's question set sends structured criteria, so AI/ML API may reject every request with HTTP 400 (shown as "Request rejected as invalid"). This is unverified: we have no AI/ML API key. Run Test connection before relying on this route; it sends the same main question as a live check.

After you have a key

Run Test connection in Formsieve. It reports the billing state separately from key problems: "key invalid", "key valid, but no credit" and "add a payment method" each come with a link to the right page. See Troubleshooting.