Audit

A written architecture report of your agent workflow, at a fixed price.

We read what you actually run — hosts, models, tools, fetch, keys, meters. You get a report ranked by engineering risk. Not a sales deck. Not a certification. Not an implementation.

What you receive

  • Swift ($100.00) — a short written note from a skim of the submission. Main risks only. Little or no diagram.
  • Ample ($200.00) — a structured report plus at least one architecture diagram of your described workflow.
  • Elaborate ($400.00) — full report: diagrams, ranked findings, recommended changes, explicit out-of-scope. Includes a follow-up round of questions.

Delivered as a written artifact (Markdown, PDF, or both — you choose). First human response in 1–7 business days is acknowledgement / start of work, not “report attached.” Report delivery then follows the SKU.

The service

You submit a brief, we investigate at the depth you paid for, you receive a written report01You submittitle, stack, files02We investigatedepth = SKU03You receive a reportfindings + diagram
We do not attach to your pipe, mint a key, or change production.

A typical workflow we read

A typical agent workflow: host, model providers, tools, and public fetch, with the eight failure modes on the hopsHostCursor / app / CIModel labsreplay / prefillTools / APIsunmetered hopsFetchrobots / PIIkey sprawl · no session record · multi-provider · no spend capYour system will differ. The report is drawn from what you upload.

What we look for

  • Replay waste

    Retries, agent loops, and CI prompt suites re-buy the same model call.

    Where identical or mechanical repeats still hit the lab, and what it costs.

  • Prefill growth

    Every turn resends the whole transcript. Cache breakpoints missing or misplaced.

    How context growth is billed today, and where a breakpoint would land.

  • No session record

    Calls happen. Nothing signed or independently checkable survives.

    What an auditor could prove after the fact from the workflow you run.

  • Key sprawl

    Provider keys in agents, CI, and laptops. No single crossing to meter.

    Where secrets live and which hop could become the one meter.

  • Unmetered tool / API calls

    Mid-session third-party calls with no ledger.

    Which tool hops are invisible to cost and to review.

  • Uncontrolled fetch

    Public web or RAG ingest without robots, SSRF, or PII gates.

    What the ingest path actually does, and which gates are missing.

  • Multi-provider drift

    OpenAI vs Anthropic vs local, no common meter or identity.

    How identities and bills split across labs in this stack.

  • No spend control

    No hard or soft cap, no cost-center split, surprise bills.

    Where a cap could sit without pretending to govern the agent.

Timeline

  1. Day 0 — pay, then submit the brief and any attachments.
  2. Days 1–7 — first human response (start of work).
  3. Then the report — Swift from the submission only; Ample after reading attachments; Elaborate after a follow-up round. No same-week guarantee for Elaborate.

Fixed prices

  • Swift

    $100.00One-time. USD. Not a seat, not meters.

    • Skim of the submission only.
    • Short written note: main risks, little or no diagram.
  • Elaborate

    $400.00One-time. USD. Not a seat, not meters.

    • Attachments plus a follow-up round of questions.
    • Full architecture report: diagrams, ranked findings, recommended changes, explicit out-of-scope.

Honesty

This is not Intermediate. It does not mint a pipe key and does not attach meters. It is not a SOC2 or legal opinion, and it is not implementation work. The report is confidential to the buyer. If a receipted crossing would help the architecture, that can appear as an engineering observation — not as a sales close.

All resources → · If you wanted the pipe, not a report →