What your customers get
An AI agent on a small appliance in their office. Their staff talks to it in plain language: "Which apprentices have three absences this month?" "Draft a follow-up note for the case manager." "Match these students to the new job opening."
The agent reads and acts on their data through your existing API — same roles, same permissions, same audit trail. It's not a superuser. It's a new staff member that follows the same rules as everyone else.
Your customer's data stays on their hardware. The agent, the keys, the conversation history — all on a device they own. You don't host the agent. You don't see the prompts. You just ship the API surface.
What you do
One thing: add a thin proxy to your existing API. It takes your existing REST endpoints and exposes them as tools the agent can call. Roughly 200 lines of code. Your validation, audit logging, and side-effects all run unchanged — the proxy just forwards the call.
You don't rewrite controllers. You don't change your auth model. You don't host anything new. The proxy is additive — your existing REST API keeps working exactly as before.
How the agent respects roles
The agent uses an API key that's scoped to a role. A registrar can create students. A case manager can acknowledge shortfalls. An instructor can post attendance. The agent only reaches what the role permits — your existing permission system enforces it, not us.
| What the agent does |
Example |
| Reads and summarizes |
"Which apprentices have 3+ absences this month?" |
| Surfaces candidates |
"These 5 students match the new job opening." |
| Drafts for human approval |
Drafts follow-up notes for the case manager to review |
| Acts after confirmation |
Posts attendance after the instructor confirms |
| Runs autonomously on routine cycles |
Archives completed cohorts at term end |
How to get there
Build it yourself
We publish an open-source reference implementation and a developer guide. If you have an engineering team, you can add the proxy in an afternoon. Your customers pay the qbit platform subscription ($50-75/mo per appliance). Community support only.
Developer guide and reference coming soon.
We build it for you
Don't have the bandwidth? We build the proxy, design the tool surface, test it against a live agent, deploy to your environment, and train your team. Our builder agents do the heavy lifting — a human reviews and approves every line.
|
What's included |
Timeline |
Price |
| Guided |
API audit, tool design, proxy build, testing, deployment, team training |
1-2 weeks |
$5K-$15K |
| Deep |
Everything above + custom prompt engineering, role-to-permission workflow design, multi-customer deployment, co-branded case study |
3-6 weeks |
$15K-$35K |
Both include the per-customer platform subscription ($50-75/mo per appliance). The integration fee is one-time; the subscription is recurring.
Why this works
- You don't rewrite anything. The proxy forwards to your existing controllers. Your validation, audit log, and side-effects run unchanged.
- Your customer owns the runtime. The agent lives on their hardware. You don't host it, you don't see the prompts, you don't store the conversation.
- Your permissions are the boundary. The agent's API key is role-scoped. It only reaches what the role allows.
- If you have a REST API, you're already agent-native. The proxy is additive, not a rewrite.
First step
A 1-2 hour call. We review your API, map endpoints to agent tools, identify the permission model, and send you a fixed-quote proposal. No commitment.
Book a scoping call
Prefer to self-serve? The developer guide and reference implementation are coming soon. Get a qbit agent in the meantime.
Looking for an agent for yourself, not your product? Visit our consumer site.