the guides

26 questions, answered in full.

26 questions about running AI agents, each answered at the length the question takes rather than the length a product page has room for: Connect OpenAI billing, Connect Anthropic billing, Connect xAI billing, Connect Google Cloud billing, Explain the gap in your AI bill, Give Claude Code a spend boundary, AI agent governance, Prompt injection defence, The EU AI Act for agent deployers, LLM cost control, The agent permissions model, Audit evidence for agent actions, MCP tool server security, Shadow AI discovery, AI agent security, LLM gateway architecture, Observability and governance, Self-hosted or hosted governance, AI agent incident response, Agent-to-agent delegation, LLM data residency, The AI vendor questionnaire, Measuring AI agent risk, Policy as code for AI, Agent onboarding, Why agents need different controls. Every answer names the mechanism and states its own limit beside its claim.
Questions, each answered on its own merits
26
Sections of argument beneath them
132
Numbered steps you can act on today
142
Follow-on questions answered in full
112
Check your AI spend assumptions

Record what each source tells you, estimate token costs with your own rates, and see where evidence still needs checking. Each currency and cost basis keeps its own subtotal.

start from the question

Which of these did you come here with?

  1. provider billing setup

    How do I connect OpenAI billing to Token Observe?

    Connect OpenAI billing
    Check the scope

    A complete retrieval does not make the provider bill final or recover historical conversations.

  2. provider billing setup

    How do I connect Anthropic billing to Token Observe?

    Connect Anthropic billing
    Check the scope

    A complete retrieval does not make the provider bill final or recover historical conversations.

  3. provider billing setup

    How do I connect xAI billing to Token Observe?

    Connect xAI billing
    Check the scope

    A complete retrieval does not make the provider bill final or recover historical conversations.

  4. provider billing setup

    How do I connect Google Cloud billing to Token Observe?

    Connect Google Cloud billing
    Check the scope

    A complete retrieval does not make the provider bill final or recover historical conversations.

  5. billing reconciliation

    Why does our AI bill differ from our token estimate?

    Explain the gap in your AI bill
    A review workflow

    The worksheet does not connect an account, import a bill or automatically reconcile a product ledger.

  6. coding agent walkthrough

    How do I give Claude Code a budget and inspect its evidence?

    Give Claude Code a spend boundary
    Routed API use

    This controls supported gateway traffic, not a Claude subscription seat or a client that bypasses the gateway.

  7. THE FIELD, DEFINED

    What is AI agent governance, and what does it require?

    AI agent governance
    What governance cannot reach

    Any agent that never routes through it, which is a discovery problem first

  8. INDIRECT INJECTION

    How do you defend an AI agent against prompt injection?

    Prompt injection defence
    The limit

    A phrasing nobody wrote a pattern for scores zero, and the rule never fires

  9. DEPLOYER OBLIGATIONS

    What does the EU AI Act require of an organisation deploying AI agents?

    The EU AI Act for agent deployers
    What no tool can do for you

    Classify your risk tier, run the assessment, or notify the authority

  10. HARD BUDGETS

    How do you stop AI agent spend running away?

    LLM cost control
    The cost of a hard ceiling

    One potentially billable egress: no retry, no failover on that call

  11. LEAST PRIVILEGE

    How should you model what an AI agent is allowed to do?

    The agent permissions model
    What this layer cannot see

    Argument values. Refunds over £200 is a policy, not a permission

  12. TAMPER EVIDENCE

    What counts as audit evidence for an AI agent’s actions?

    Audit evidence for agent actions
    The default

    Unkeyed, a rewrite that recomputes every hash verifies clean

  13. TOOL SURFACE

    How do you secure Model Context Protocol tool servers?

    MCP tool server security
    What is withheld rather than inspected

    Image, audio, blob and resource content, after the tool has already run

  14. COVERAGE FIRST

    How do you find AI use that is not going through your controls?

    Shadow AI discovery
    How current a finding is

    As current as the export it was computed from

  15. THE WHOLE SURFACE

    How do you secure an AI agent?

    AI agent security
    What none of it reaches

    An agent that calls a provider directly, and any media it sends

  16. THE REQUEST PATH

    How should an LLM gateway be architected?

    LLM gateway architecture
    The topology this assumes

    One process and one write path; no multi-replica or high-availability claim

  17. TWO DISCIPLINES

    Do I need agent observability or governance, or both?

    Observability and governance
    What neither reaches

    An agent that routes through neither, and the model’s hidden reasoning

  18. WHERE IT RUNS

    Should AI governance run in my own network?

    Self-hosted or hosted governance
    What self-hosting does not settle

    Support access, incident handling and evaluation terms are still a legal question

  19. WHEN IT GOES WRONG

    What do you do when an agent does something it should not have?

    AI agent incident response
    The limit of erasure

    It reaches the live database; snapshots and some tables are outside it

  20. INTERSECTION

    How should one agent be allowed to ask another for something?

    Agent-to-agent delegation
    What intersection does not bound

    Why the upstream agent asked: a legitimate grant, exercised for an injected reason

  21. RESIDENCY

    How do you keep agent traffic inside a jurisdiction?

    LLM data residency
    The assertion nobody can verify

    No control can prove where a vendor served a request

  22. PROCUREMENT

    What should you ask an AI vendor?

    The AI vendor questionnaire
    What this exercise is not

    A questionnaire is a filter; it does not replace testing the product yourself

  23. RISK, MEASURED

    How do you decide which agents are risky?

    Measuring AI agent risk
    What the tier does not do

    It is not a policy-scope dimension; rules bind on agent id, team and tag

  24. TESTABLE RULES

    How do you express an AI policy so it can be tested?

    Policy as code for AI
    What a compiled artefact is not

    A policy exported to another engine covers matching, not the enforcement around it

  25. PROTOTYPE TO PRODUCTION

    How do you take an agent from prototype to governed production?

    Agent onboarding
    What a readiness check cannot tell you

    Release provenance, independent testing, legal approval or your integration matrix

  26. THE GAP

    Why don’t existing API controls work for agents?

    Why agents need different controls
    What reusing the stack cannot fix

    An agent that never routes through any of it

the questions underneath

112 narrower questions, and where each is answered.

Connect OpenAI billing

Connect Anthropic billing

Connect xAI billing

Connect Google Cloud billing

Explain the gap in your AI bill

Give Claude Code a spend boundary

AI agent governance

Prompt injection defence

The EU AI Act for agent deployers

LLM cost control

The agent permissions model

Audit evidence for agent actions

MCP tool server security

Shadow AI discovery

AI agent security

LLM gateway architecture

Observability and governance

Self-hosted or hosted governance

AI agent incident response

Agent-to-agent delegation

LLM data residency

The AI vendor questionnaire

Measuring AI agent risk

Policy as code for AI

Agent onboarding

Why agents need different controls

If the question that would decide it for you is narrower than any of these, the FAQ answers the ones buyers ask before committing, including the ones with uncomfortable answers.

Read the questions buyers ask
Your next step

The guides argue it. An evaluation settles it.

Create a cloud account and workspace. No card or server installation. Model calls and Google BigQuery scans can incur separate provider charges.