Operating ProcedureExecution layer

endlesstokens Pass Procurement and Key Provisioning (Onboarding)

A sequence with 7 steps: Confirm the client workflow is ready to execute before payment.

By InnovaAI ResearchPublished

What are the steps?

sequence

endlesstokens Pass Procurement and Key Provisioning (Onboarding)

  1. 01

    Confirm the client workflow is ready to execute before payment

    The pass window starts at payment, so a 1-hour pass bought during scoping burns out before any agent runs. Get the client's repo, prompt set, and target agent named in writing first.

  2. 02

    Select the pass duration against the client's session shape

    1-day pass at $15 and 3-day pass at $36 both carry no token or request cap. A 1-hour pass suits a single smoke test; a 3-day pass suits a multi-day agent-assisted build. Buy the shortest window that covers the scheduled work.

  3. 03

    Generate the account API key and store it in the agency secrets manager

    Pair the key with the base URL https://api.endlesstokens.ai/v1. One key per client account, since endlesstokens has no multi-tenant client isolation.

  4. 04

    Point the first coding agent at the gateway

    Supported clients include Aider, Cline, Claude Code, Codex, Kilo, OpenCode, and Roo. Configure the OpenAI-compatible or Anthropic-compatible endpoint depending on which the agent expects.

  5. 05

    Verify the et:auto router and image path with a real prompt

    Send one prompt that exercises et:auto model selection and one request carrying up to 5 images. Confirm the response lands inside the 128K context window before handing the endpoint to the client team.

  6. 06

    Test the two-session-per-key cap under load

    Run two parallel sessions, then attempt a third. Document the failure mode so the client team knows to serialize work rather than open extra agent tabs mid-delivery.

  7. 07

    Hand off the endpoint with a self-serve procurement note

    Give the client the pass purchase steps and the renewal cadence for their retainer. Flag that each additional client needs their own account and key, not a shared agency key.