underpin/ optimise
CONTEXT OPTIMISATION API

Reduce token spend
on your AI agents.

Send less text to your AI model. Spend less on input tokens. Optimise picks out relevant information from your documents and tool results before your agent makes its model call.

Free account · 100 requests/day · No card required

Benchmark result

FEWER TOKENS. SAME TASK.

The same tasks, with and without Optimise

Without Optimise194,420 tokens
100%
With Optimise85,935 tokens
44.2%
55.8%fewer tokens used

Benchmark result, not a guaranteed saving. Savings and accuracy vary by task and model. See the results →

01 / HOW IT WORKS

Reduce AI token costs with one API call.

Illustrative workflow

Source documents

Documents, tool results, knowledge

QUERY / What is the payment deadline?
underpinoptimise

Relevant context

[1] Payment terms
[3] Invoice requirements
[7] Supporting detail

Exact excerpts · source offsets retained

Your agent

Answer with evidence
Get more detail when neededKeep more context when needed

01 / Read the source and question.

Example workflow
02 / SAVE ON TOKENS

Fewer tokens. More room in your budget.

Use fewer tokens. See what you could save.

TOTAL TOKENS
194,42085,935
55.8%

Fewer tokens used

A measured reduction across complete agent tasks. See the docs for results and limitations.

PER MILLION TOKENS
1,000,000442,000
558k

Fewer tokens per million

What the same reduction would mean per million tokens. Your results will vary.

KEEP THE SOURCE
Your documents → relevant context
Stay connected

Know where the context came from

Keep a link back to the original text, so your agent can ask for more detail when it needs it.

What could you save per million input tokens?

At £10 per million input tokens, a 55.8% reduction would bring that input cost down to £4.42 — a saving of £5.58.

Illustration only. Actual savings depend on your model, caching and any extra requests. Optimise is free within the beta limits.

See how savings are measured →

Fewer tokens do not always mean a lower total bill. Check answer quality and costs on your own tasks.

FITS YOUR WORKFLOW

Keep your model. Send less context.

Add Optimise before your existing model call. Send us your source text and a question, then pass the returned context to your model. Your application stays in control.

Use the returned text in your own model request. Results vary by provider; these links do not imply a tested integration or partnership. See how to connect →

BUILT WITH YOUR FEEDBACK

Build Optimise with us.

Trying it in a side project? Putting it through its paces at work? We’d love to hear what you’re building, what helps and what gets in the way.

Talk to the team hello@underpin.cloud

Show us what you’re building.

Share your workflow, an experiment or something you’d like Optimise to make possible.

Help shape what comes next.

Feature ideas, rough edges and honest feedback are all welcome. Tell us what would make it more useful to you.

Stuck? Ask us.

Questions about the API or an unexpected result? Send us a small example with any private data and API keys removed.

You don’t need a polished use case to join the conversation.

03 / START FOR FREE

Your account. Your API key.

Create an account and start using Optimise. Your key does not expire. 100 free requests each day, resetting at midnight UTC. No card required.

Sign in again if you refresh or close this page. Keep your API key somewhere safe.

Start saving tokens.

  • 100 free requests a day.
  • An API key that does not expire.
  • Setup guides for code and workflow tools.
  • No card and no automatic paid upgrade.

Keep your key on your server or in your workflow’s credential store.

Free beta. Input and shared capacity limits apply. View limits and account details →

Read the integration guide →
04 / HELP US IMPROVE

Tell us what worked. And what didn’t.

Tell us how Optimise fits your workflow or where you got stuck. Add your API key above to send feedback.

Privacy and beta limits

Documents are processed on Cloudflare and not stored by this application. We store your email, salted and peppered password hash, recovery-code hash, API-key hash and usage counters. Email is your login identifier; verification and email reset delivery are not yet available. Save your recovery code. Delete your account above to remove login data and revoke access.

Daily salted IP hashes help limit abuse; raw IPs are not stored by the application. Daily abuse and usage records are cleaned within three days, expired sessions daily and feedback within 31 days. Cloudflare processes network metadata under its own policies.

Free public beta without a production SLA. Evaluate answers on your own tasks. Full limits and privacy →