Identity and workspace scope
Bind an IAM-issued identity to server-derived organization and workspace context before model dispatch.
Osyra decision traceVerified engineering capture · b1c7cbcd · July 20, 2026
The enterprise AI control plane
Run an AI workforce.Keep every action under control.
Across your organization, Osyra gives people and agents one governed path to enabled models and providers—with identity, policy, routing, cost attribution, and evidence organized around the request.
See one verified request move through the control plane. The captured run ends at Cost.
Captured request · ends at CostCAPTURED PATH
Complete decision trace · final state
- A streaming AI request enters with customer content withheld from the visual.
- A verified OAuth identity and server-bound workspace scope attach at the edge.
- Authentication and execution authority resolve before model dispatch.
- The logical model resolves to the enabled workspace runtime with its artifact digest pinned.
- Unary and strict streaming agree on 47 prompt tokens — 1 uncached and 46 read from the prompt cache — and 10 completion tokens.
- A signed linear.v1 price, independent oracle, response, and Billing ledger agree on $0.000001 — an exact 100 microcents.
- A separately proven attested path persists a signed inference receipt.
- AP00016 independently verifies the persisted receipt and returns valid.
- A signed and chain-linked durable audit event records the correlated Billing operation.
- Verified Memory carries signed evidence in a portable .ome archive as a separate proven capability.
- A streaming AI request enters with customer content withheld from the visual.
- A verified OAuth identity and server-bound workspace scope attach at the edge.
- Authentication and execution authority resolve before model dispatch.
- The logical model resolves to the enabled workspace runtime with its artifact digest pinned.
- Unary and strict streaming agree on 47 prompt tokens — 1 uncached and 46 read from the prompt cache — and 10 completion tokens.
- A signed linear.v1 price, independent oracle, response, and Billing ledger agree on $0.000001 — an exact 100 microcents.
- A separately proven attested path persists a signed inference receipt.
- AP00016 independently verifies the persisted receipt and returns valid.
- A signed and chain-linked durable audit event records the correlated Billing operation.
- Verified Memory carries signed evidence in a portable .ome archive as a separate proven capability.
Why Osyra exists
AI is becoming an operating layer. Accountability has to become one too.
The next decade of enterprise software will be written by models. For requests that run through Osyra, identity, authority, route, usage, cost, and evidence stay connected—so platform, security, and finance teams investigate the same event.
The enterprise control plane
One control plane. Every enabled model. Every published policy.
Identity, policy, routing, cost attribution, receipts, audit, and memory—organized around the request instead of scattered across tools.
Before inference · AuthorityKnow who can act.
Roles and permissions
Resolve operation authority on the server instead of accepting client-supplied ownership or privilege.
Virtual provider keys
Give applications a stable Osyra credential while provider secrets remain behind the control plane.
Before inference · GovernanceDecide what is allowed.
Versioned policy bundles
Publish reviewable rules for model access and request handling before an enabled runtime receives traffic.
Inline request controls
Apply served-path controls for sensitive data, prompt risk, model access, and workspace constraints.
Budget visibility
Keep workspace budgets and threshold state visible without presenting request-time hard stops as universal today.
During inference · ExecutionRun through one path.
Logical model routing
Address a configured logical model while the signed runtime registry resolves an enabled execution target.
Provider and private endpoints
Operate enabled provider routes and registered private endpoints under the same workspace authority.
Usage and cost attribution
Carry model, provider, workspace, token usage, and pricing provenance into attributable Billing evidence.
After inference · ProofKeep what proves it.
Independent receipt verification
Persist and independently verify signed inference receipts on receipt-enabled paths.
Signed, chain-linked audit
Record correlated operations with signature and chain-link evidence on verified audit paths.
Portable Verified Memory
Carry signed evidence in portable .ome artifacts on separately proven memory paths.
Inspectable evidence
Proof you can inspect.
A captured request proves inference and cost. Separate live gates establish receipts, independent verification, signed audit, and portable memory. Each boundary stays visible.
Captured live path
b1c7cbcdReal inference. Exact usage. Exact charge.
A verified integration run crossed IAM, Edge, Broker, an enabled inference runtime, and Billing. The figures below describe that capture—not throughput, scale, or a universal result.
- Runtime
- configured runtime · artifact digest pinned
- Usage
- 47 prompt · 10 completion
- Prompt cache
- 1 uncached · 46 cache-read
- Cost
- $0.000001 · response = exclusive ledger
- Ledger unit
- 100 µ¢ exact · 1 USD = 100,000,000 µ¢
- Pricing
- signed linear.v1 · independent HALF_EVEN oracle
Verified integration capture · July 20, 2026 · customer content withheld from this visual
Separately verified proof fabric
live gatesReceipts, re-decision, audit, and portable memory.
Separate live gates establish the evidence capabilities around the request path. The boundary stays visible so “verified” always means something inspectable.
- Receipt
- signed inference receipt persisted
- Verifier
- AP00016 independent result · valid
- Audit
- correlated Billing operation · signature + chainlink present
- Memory
- portable .ome artifact · separate Verified Memory capability
Receipt and audit: e2e/yc-demo/verify.sh · Verified Memory: separately proven enabled path
The control plane for accountable AI