Elements Codebase

Overview

Elements Codebase carries the largest input allowance on the platform. The work it exists for, migrations and refactors and tracing a call through a system, is exactly the work that fails when the model can only see one file. It is the most expensive Elements version, and the one that saves the most time when the alternative is a human reading forty files first.

How it behaves

Carries a whole repository.

Speed and depth trade against each other across a family. The faster versions cost more per rung, not less: what is being bought is a shorter wait, and reserving capacity to answer promptly costs more than using it whenever it is free.

Choosing this model

Reach for it when

• Migrations and cross-file refactors
• Tracing behaviour through an unfamiliar repository
• Reviews that must consider callers as well as the change

Reach for something else when

• Use elements when the change is contained to one file.
• Use elements.fast when you need a small edit quickly.

Others in the Elements family

• Elements: The coding model. Edits, reviews and builds.
• Elements Fast: Single-file edits and short-range changes, tuned for latency.

Example

curl https://evaesi.dev/api/v1/responses \
  -H "Authorization: Bearer esi_dev_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "elements.codebase",
    "prompt": "Explain what this service does."
  }'

Pricing

Published rates for this model, read live from the platform. API usage is billed at these rates; subscription plans draw from a monthly allowance instead, shown below.

Limits

Plan terms

Subscription plans include a monthly rung allowance on each model, and apply a multiplier when drawing that allowance down. API usage is billed at the rates above and is not drawn from a plan allowance.