LINE — a persistent telephone identity
- Dedicated, local numbers per agent
- Inbound and outbound, from one identity
- Number lifecycle: reserve, port, release
- Owned by the agent, controlled by you
DEVELOPER PREVIEW/AGENT COMMUNICATIONS INFRASTRUCTURE
ORDan gives AI agents dedicated phone numbers, voice, messaging, permissions, and an auditable identity — through one API.
This demo simulates: an agent requests a phone identity, the owner approves scoped permissions, a number is provisioned, the agent requests a call, a policy check authorizes it, the call routes through the carrier network, connects, completes, and is recorded in the ledger.
Q·01
WHOis this agent?
A durable identity, issued to the agent itself.
Q·02
WHATmay it do?
Capabilities, policies, and ceilings you define.
Q·03
HOWdoes it reach out?
A real number, for voice and messaging.
Q·04
WHATdid it actually do?
A sealed record of every action and outcome.
01 — THE THESIS
Agents can browse the web, write software, analyze data, purchase services, and execute workflows. But enormous parts of the real economy still run through phone calls and text messages.
ORDan gives autonomous software a persistent communications identity for that world. Not a louder agent — a line.
02 — CAPABILITIES
Five primitives, one principal. Each answers one of the four questions — and each is exposed through the same API.
03 — AUTHORIZATION
Agents don't get keys to the kingdom. They request capabilities; a human grants them — scoped, bounded, and reversible. Try it: flip the switches, set the ceiling, authorize.
Visit the pairing URL and approve the request:
The agent holds nothing yet — not even a number.
EXECUTIVE ASSISTANT requests permission to:
Credential issued to the agent's runtime. Line provisioned.
Authority lives outside the context window. The credential is bound to the agent's runtime — never pasted into a prompt, exposed to the model, or stored in its memory. The agent can act only inside what you approved. Nothing more.
A·01
Granted — every capability is an explicit grant from an owner, not a default.
A·02
Scoped — read replies ≠ send messages ≠ place calls. Granular by design.
A·03
Revocable — withdraw one capability or the whole line, instantly.
04 — POLICY ENGINE
Every attempted communication passes a policy layer before the network is touched. Select a scenario and watch the same engine authorize, hold, or refuse.
“Call Dr. Patel's office and move Tuesday's appointment to Friday afternoon.”
Call authorized and executed.
ORDan is a permissions engine, not a compliance claim. Policies are yours to define and enforce — before a single digit is dialed.
05 — API
Provision identity. Request action. Get proof. The policy engine runs before the network does — so "call someone" is an auditable event, not a side effect.
RESPONSE — 201 CREATED
LIFECYCLE
OUTCOME
06 — MCP
Every ORDan capability is an MCP tool. Your agent doesn't need to be rebuilt around us — it needs authority and a channel. It already knows how to call tools.
07 — MODEL-NEUTRAL
We'll handle how it reaches the world. ORDan does not own the intelligence — it provides the real-world communications capability underneath it.
Compatibility means capability, not partnership. No endorsement implied.
08 — A DIFFERENT PRIMITIVE
LEGACY TELEPHONY
Authenticates an account. Anyone holding the key is the account. What the key does is nobody's memory.
ORDAN
Authenticates the agent — and its authority, and its intent. Every step is an accountable principal acting on a record.
ORDan treats an agent as a persistent principal — identity, capabilities, authority, budget, history, and revocation. That is the architecture.
+1 212 555 0148
AGENT-OWNED IDENTITY · US · NEW YORK
LAST ACTION — Appointment rescheduled · 2 min ago
09 — FLAGSHIP PRIMITIVE · ORDAN LINE
An ORDan Line is a persistent phone identity for an autonomous agent — with capabilities, an owner, a policy, a budget, and a history attached. It behaves like an identity object, not a VoIP rental.
This interface is a Developer Preview simulation. Try REVOKE — then imagine it at fleet scale.
10 — LEDGER
Policy decisions, connections, transcripts, outcomes, cost — appended in order, sealed, queryable. The flight recorder for autonomous software.
REQUESTED BY
executive-assistant
PURPOSE
appointment_reschedule
AUTHORIZATION
owner_delegated
POLICY
personal_assistant_v1
DECISION
allowed
RECIPIENT
+1 212 *** 0123
STARTED
14:32:18
CONNECTED
14:32:24
COMPLETED
14:35:28
DURATION
03:04
TRANSCRIPT
available
RECORDING
available
11 — USE CASES
12 — ARCHITECTURE
The agent runtime remains yours — any model, any framework. ORDan is the controlled boundary between autonomous software and the physical network.
Model-neutral. Framework-neutral. The intelligence stays in your runtime — the authority, the channel, and the record live in ours.
13 — SECURITY & TRUST
Every agent capability should be granted, scoped, observable, and revocable. Nothing is implicit; nothing is assumed; nothing is unrecorded.
We make no certification claims on this page. Our security posture will be published as it is independently verified — not before.
Scoped agent credentials
Every key belongs to an agent principal — never to a human, never to a browser session.
Least-privilege by default
An agent starts with nothing. You grant exactly what a task requires.
Revocable access
Withdraw one capability or the entire line. Authority ends the moment you say so.
Configurable spend limits
Hard ceilings per action, per line, per month. Exceeding them is refused, not billed.
Action policy evaluation
Intent is checked against your rules before the network is ever touched.
Secret isolation
Credentials live in the runtime — never in a prompt, a transcript, or a context window.
Immutable-style event history
The ledger appends. It does not rewrite.
Owner authorization
No capability exists without a human grant behind it.
Auditability
Every decision, connection, and outcome is reconstructable after the fact.
14 — DEVELOPER PREVIEW
The Developer Preview includes the full primitive set — so you can build the agent you're already planning, on infrastructure that takes authority seriously.
Usage-based telecom charges and production pricing will be published before general availability. No fake discounts, no countdowns, no "limited spots."
We'll email you when your Developer Preview access opens. You'll hear from a person — not a sequence.
15 — FAQ
ORDAN · DEVELOPER PREVIEW
ORDan connects autonomous software to the phone network — with identity, authority, and accountability built in.