Authentication Tokens - Jelou AI Docs

What are runtime tokens?

Runtime tokens (prefix jfn_rt_) are legacy credentials that authenticate requests to functions deployed before the migration to platform API keys. Functions deployed today don’t receive any runtime token — they use a platform API key from the first deploy.

Creating new runtime tokens (jelou functions tokens create) is deprecated and responds 410 Gone. Deploys don’t generate one automatically either. If your function is new or you lost your runtime token, use a platform API key.

How to use

If your function already had an active runtime token before the migration, it still works: send it in the X-Jelou-Token header:

curl -X POST https://my-function.fn.jelou.ai \
  -H "Content-Type: application/json" \
  -H "X-Jelou-Token: jfn_rt_abc123..." \
  -d '{"phone": "593987654321"}'

Rule	Detail
Header	`X-Jelou-Token` (legacy runtime tokens are not validated via `Authorization: Bearer`)
Format	Header only — not query param, not body
Max size	4 KB
Missing token	`401 { "error": "Unauthorized" }`

CLI management

# List tokens
jelou functions tokens list my-function

# Revoke a token — still works
jelou functions tokens revoke my-function <token-id> -y

Revoking a token triggers an automatic redeploy. Clients using that token will start receiving 401 once the redeploy completes.

Creating additional tokens (deprecated)

jelou functions tokens create my-function --name ci-deploy
# ✗ 410 Runtime tokens are deprecated. Create an API key in the apps
#   configuration section (https://apps.jelou.ai) and send it as
#   `Authorization: Bearer <key>` when invoking the function.

Creating new runtime tokens is no longer possible. Use a platform API key instead — see below.

Multiple tokens

If your function already has multiple active tokens from before the deprecation (one per environment, service, or team), you can still list and revoke them individually. Revoking one doesn’t affect others.

Lost token?

You can no longer generate a replacement via the CLI. Instead:

Create an API key at apps.jelou.ai
Send it as Authorization: Bearer <key> — see recommended alternative
If the old runtime token was compromised, revoke it: jelou functions tokens revoke my-function <id>

Recommended alternative: API keys

The supported mechanism for authenticating new functions (every new deploy uses this from the start) or replacing a lost runtime token is a platform API key, not a runtime token:

curl -X POST https://my-function.fn.jelou.ai \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer sk_..." \
  -d '{"phone": "593987654321"}'

See the authentication guide for the full flow.

Brain Studio

Configure your function as an external MCP server using your API key:

Field	Value
URL	`https://my-function.fn.jelou.ai/mcp`
Header name	`Authorization`
Header value	`Bearer sk_...`

If your function is legacy and still uses a runtime token, use X-Jelou-Token / jfn_rt_abc123... instead. See the Brain Studio guide for the full flow.

​What are runtime tokens?

​How to use

​CLI management

​Creating additional tokens (deprecated)

​Multiple tokens

​Lost token?

​Recommended alternative: API keys

​Brain Studio

What are runtime tokens?

How to use

CLI management

Creating additional tokens (deprecated)

Multiple tokens

Lost token?

Recommended alternative: API keys

Brain Studio