console.typesafe.ai (console + playground)

TL;DR https://console.typesafe.ai is where you log in (Google or emailed code), try Jev in the Playground at /playground, and get an API key at /settings/keys. The Master Customer Agreement names it the "Web Interface" and the hosted API the "API"; together they are the "Services."

Facts

The captured login page (raw/site/console.txt) is only the unauthenticated screen: the two login options plus "By continuing, you agree to the terms of use and the privacy policy." Everything behind the login is not captured, so the surface described below is what the docs and the MCA state, not what was observed.

What you do with it

From the Quick start (raw/docs/introduction__quickstart.md):

Try it: the Playground

1. "Open the Playground and log in."
2. "Paste any text" as the state — the sample state used is: Hi, I've been trying to connect my Stripe account for 3 days and it keeps failing. I'm losing sales. Please help ASAP.
3. "Add a question." The sample is a Noul:

{
  "urgency": {
    "type": "noul",
    "instructions": "Does this message express urgency?"
  }
}

4. "Add more questions. Mix Noul, Choice, and Score in one call and see all results at once."

Call it: the API

1. "Get your API key from the dashboard"
2. POST to https://api.typesafe.ai/v1/systemone with Authorization: Bearer <API_KEY>
3. Read HTTP API: POST /v1/systemone and GET /v1/models for the rest.

Share links

Playground sessions can be shared with a link of the form https://console.typesafe.ai/playground?share=shr_... (the shr_ prefix plus an opaque ID). The launch blog links "the actual query" behind its side-by-side demo this way, gated on early access: "For people with early access to TypeSafe, here is the actual query." Treat a share link as a pointer to a saved state + questions payload; the exact contents are only visible to accounts with access.

Contract terms that govern it

From the Master Customer Agreement (see Legal: MCA, DPA, privacy, data retention for the full treatment):

• §1 Overview: the Web Interface and the API together are the "Services."
• §2.4 Access Credentials: API key for the API, username and password for the Web Interface. "Customer will not authorize or enable any person or entity who is not an employee or independent contractor of Customer… to access or use the Web Interface," and credentials must not be shared.
• §2.3 License Restrictions includes "(f) publish benchmarks or performance information about the Services" — relevant if you plan to publish your own Jev measurements.
• §2.5 Updates: TypeSafe may update the Services, which "may result in the API's becoming incompatible with a Customer Application."

Related

• Quickstart: first call in HTTP, Python, JS — the full first-call walkthrough
• HTTP API: POST /v1/systemone and GET /v1/models — what the key is for
• Legal: MCA, DPA, privacy, data retention — MCA, DPA, privacy, retention
• TypeSafe AI (company) — the company
• Jev (model) — the model the playground calls

Sources

• raw/site/console.txt (https://console.typesafe.ai/)
• raw/docs/introduction__quickstart.md (https://docs.typesafe.ai/introduction/quickstart)
• raw/site/typesafe-ai-legal_mca.txt (https://typesafe.ai/legal/mca)