Quickstart
Run a real execution, with a real key, in four commands.
Every command below is against a route that exists. Nothing here is illustrative.
# 1. Read what Tessen can do. No authentication needed.
curl https://cloud.tessen.ai/api/capabilities
# 2. Create a key in the Console: https://cloud.tessen.ai/platform/keys
# The secret is shown once, and begins tsn_cloud_
# 3. Start an execution.
curl -X POST https://cloud.tessen.ai/api/execution \
-H "Authorization: Bearer tsn_cloud_EXAMPLE" \
-H "content-type: application/json" \
-d '{"goal":"a one-page site for a bakery in Lisbon","outcome":"website"}'
# -> 202 Accepted, with the plan and its stages
# 4. Read it back as it runs.
curl "https://cloud.tessen.ai/api/execution?id=<plan id>" \
-H "Authorization: Bearer tsn_cloud_EXAMPLE"What you get back
Starting an execution answers 202 with the plan already written — the id is watchable from the first millisecond, and the stages run after the response. That ordering is deliberate: a request that ran the work inline would hold a connection open through a model call and a deployment, and would leave work half done with nothing recording where it stopped.
Where the journey stops
Step 2 cannot be automated. Keys are created by a person in a browser and never by a program, so there is no endpoint that completes the Quickstart without a sign-in. Reading your own token consumption is also session-only today — GET /api/usage refuses a key. Both are measured boundaries, stated rather than worked around.
Authentication →