For UK FTA certificate jobs

Cap the UK FTA certificate. Keep the provider key.

A UK free-trade-agreement certificate workflow can keep calling a standing provider secret after its document fields are prepared. Issue a Till key for that job with a required request ceiling so remaining capacity stays readable and the worker can stop.

Controlled betaManually onboardedPublic signup is closed
One UK FTA certificate job. One envelope.

Isolate the certificate traffic, not the provider account.

  1. 01
    Issue a disposable Till key for the job

    Set the required request ceiling from expected fields and retries, then add optional token, estimated-spend, expiry, and IP bounds.

  2. 02
    The provider credential stays behind Till

    The worker uses a Till key, not an unconstrained provider secret. Revoke or expire that key when the batch is retired.

  3. 03
    This is not a customs authority

    Till does not issue certificates, certify origin, or replace an issuing body. It is a hosted control layer in front of AI providers.

A Till key is still a bearer secret.

Connect provider accounts once. Each job gets a disposable Till key with a required request ceiling and optional controls. Till is not a certificate issuer or a replacement for provider billing or IAM.

The next batch

Finish the queue. End the key.

Request Pro beta access. Till is a controlled beta; accounts are onboarded manually.