One engagement. One usage record.

Create a client key with a budget and expiry, download tool configs and export the usage for client billing.

Launch feature preview. The engagement portal is being verified; this page describes the intended workflow, not a live demonstration.

Create an engagement key

In the engagement launch kit, enter a client reference, a USD budget and an expiry date. Choose which Redline models the key may use.

Use a client reference rather than a confidential client name where practical.
The key budget limits its quota; it does not add funds to the account.
Expiry stops future requests after the chosen time. Check the displayed timezone.
Store the key securely when it is shown. Keep each engagement’s credentials separate.

Download the tool configuration

The portal is designed to offer a Claude Code settings file, a Codex profile when supported, an environment file and a connection-test command. Config downloads may contain the key: treat the files as secrets and keep them out of version control.

Codex remains coming soon. Check the published compatibility status before choosing a tool.

Test before you start work

Run the connection test with the engagement key. It makes a billable one-token completion. Then perform a small task in your chosen tool and check that usage is attributed to the correct engagement.

Bash / zsh

curl --fail-with-body --silent --show-error "https://api.redline-api.duckdns.org/v1/models" -H "Authorization: Bearer $REDLINE_API_KEY" && curl --fail-with-body --silent --show-error "https://api.redline-api.duckdns.org/v1/chat/completions" -H "Authorization: Bearer $REDLINE_API_KEY" -H "Content-Type: application/json" -d '{"model":"redline-core","messages":[{"role":"user","content":"Reply OK"}],"max_tokens":1}' && printf '\nOK\n' || { printf '\nFAIL: inspect the HTTP error above\n'; exit 1; }

Export client usage

Select an engagement and date range, then choose CSV or a printable summary. The export includes request counts, uncached/cached/output tokens and the usage cost at your API rate.

Optional markup is displayed separately as a “billed to client” column.
Prompts and model responses are not part of the export.
Review the date range, timezone and totals before sending it to a client.
Use your accounting system for the actual invoice; the export is supporting evidence.

Close the engagement

Export the final usage record and revoke the key when the work is complete. Expiry provides a fallback, but a deliberate closeout avoids leaving unused credentials active.