Know who’s behind the agent.
Short-lived, task-scoped credentials carry the human → agent → sub-agent chain. The person who started the work remains attributable, while provider keys stay at the broker edge.
Identity & control for enterprise AI
Give agents access.Keep control.
Connect your people, agents and models through one policy boundary. Know who made the request, where the data went, and why it was allowed.
01 / attributed originHuman↳ Agent
One short-lived identity, scoped to the task.
02 / control boundaryNeptic.
IdentityPolicyBudgetDLP
Decisions happen before the provider call.03 / approved routeModel
Allowed destination only
04 / evidenceDecision record
Identity · route · spend · outcome
✓ Served / approved and recorded⊘ Refused / stopped and recorded
Provider keys remain at the broker edge.The request path, made visible.
One boundary. Five controls that move together.
01Identity
02Policy
03Routing
04Spend
05Evidence
01 / The platform
One boundary.
Every model call.
Agents move fast. Access and accountability should move with them. Neptic evaluates every turn at the point where identity, data and model choice meet.
Decide what can leave.
Every turn is classified again, including data introduced by tools or retrieval. Policy decides which models may see that data before anything is sent.
Account for every turn.
Budget is reserved before dispatch, then reconciled with actual usage. The identity, policy, route, spend and outcome become a tamper-evident record.
02 / How it works
A clear path from request to record.
The same ordered path applies whether the destination is an external provider or a model you host.
01Authenticate
02Classify
03Authorize
04Route
05Reserve budget
06Input DLP
07Proxy
08Output DLP
09Reconcile spend
10Emit audit
Every request has a clear outcome
Served
Allowed and completed.
Refused
Policy or budget said no.
Failed
A provider or system error needs attention.
What happens along the path
Neptic authenticates the task credential, classifies the turn, and checks model and data policy. Routing chooses only within the approved set. Budget is reserved before dispatch; input and output DLP surround the proxy call. Actual usage is reconciled and the turn is recorded. A policy refusal makes no provider call. If the audit write cannot complete, the turn fails closed.
03 / Routing
Choice, inside the lines.
Identity and data policy define the models an agent may use. Routing chooses within that approved set, reserves budget before dispatch, and records why the chosen model served the turn.
See the resulting recordRoute selection / exampleIllustration
01
Candidate AExcluded by data policy
Ineligible02
Candidate BApproved for this task and data class
Selected ↗03
Candidate CApproved alternative
EligibleBudget reserved before the provider call.
04 / Evidence
The record outlives the request.
Every turn carries its attribution, policy decision, route, spend and outcome into a tamper-evident ledger. Hash chaining and signed checkpoints make later changes detectable.
Explore deploymentTurn record / exampleIllustration
record / example-001
identityHuman → agent, task-scoped
policyAllowed for this data class
routeApproved model selected
spendReserved → reconciled
outcomeServed
Linked to the preceding record
05 / Deployment
Your infrastructure.
Your policies.
Keep the enforcement path close to the data it governs. The same request pipeline runs across supported deployment modes.
01 / Managed
Multi-tenant SaaS
Organization, team and user isolation in a managed environment.
02 / Dedicated
Your VPC
A single-tenant deployment inside your cloud network.
03 / Private
On-prem or air-gapped
Kubernetes deployment where network and data boundaries require it.
Keys and access. Provider keys are injected at the proxy edge. Operators sign in through Microsoft Entra ID, and access follows your directory roles.
Control and evidence. Network egress can make the broker the only path to approved providers. Security capabilities are described here; no certification is claimed.
Practical questions
Do agents hold provider keys?
No. Agents use short-lived, task-scoped credentials. Provider keys are held at the broker edge and injected only when the approved request is proxied.
What happens when policy refuses a request?
The request is recorded as Refused. The provider is not called, so there is no provider usage to bill for that turn.
How does an organization get started?
Set up a workspace and connect your Microsoft Entra app registration. Operators then sign in through your directory.
Begin with control
Make every call accountable.
Bring agents, models and policy through one clear boundary. See each decision and keep the record.