Build with Eon.
Bring Eon models into your own tools. API access requires an approved Enterprise organization and a key issued by Eon.
Private Enterprise pilot · invited testers only
Get access
Contact Eon Technologies to arrange an Enterprise pilot. Plus and Pro workspace subscriptions do not include API keys. Access is manually approved; Enterprise pricing and wider availability are arranged directly, with no self-service checkout.
Keep keys on your server. They are shown once, expire after 90 days and can be revoked by the operator. Never put a key in browser code or a public repository.
Make your first request
Set EON_API_KEY in your server environment, then send a text completion:
curl https://eon-lexis.vercel.app/api/v1/chat/completions -H "Authorization: Bearer $EON_API_KEY" -H "Content-Type: application/json" -d '{"model":"lexis-2.1","messages":[{"role":"user","content":"Write a clear welcome message."}],"max_tokens":512}'Read the answer at choices[0].message.content. The response includes usage and a request identifier. This endpoint generates text; it does not edit workspace files or run Codie tools.
| Endpoint | Purpose |
|---|---|
| GET /api/v1/models | List Enterprise model identifiers |
| POST /api/v1/chat/completions | One bounded model response |
Models: lexis-2.1 and sienta-2.1. Both endpoints require a Bearer key.
Predictable limits
- Text messages only: 1–32 messages, up to 32,000 content characters. Large inputs may need to be shortened to fit the per-request provider budget.
max_tokens: 1–4,096; default 1,024. Optionaltemperatureis 0–2 andthinkingis a boolean. Output limits include reasoning when enabled.- Non-streaming JSON responses only in this pilot. Tool calls, attachments and automatic continuation are not exposed through this endpoint.
- Organization limits cover monthly requests, tokens, request rate and a separate provider-cost ceiling. Active reservations count toward limits; unused portions are released at settlement. API allowances are separate from workspace Eon Tokens.
- An optional UUID
Idempotency-Keyprevents duplicate model invocations. Reusing it returns 409 rather than generating or charging twice; it is not a response-retrieval endpoint.
401: invalid/expired key. 403: Enterprise approval or scope required. 409: request identifier already used. 413: request too large. 429: configured limit reached. 502/503: model or service unavailable. Keep the X-Request-Id / request_id when contacting support. Do not retry a submitted request under a new identifier unless you know it is safe to generate again.
Audit records contain identifiers, actions and usage—not prompt text, API secrets or response content. See the privacy notice.