01
Building first
Email & verification
Hosted email inboxes with custom domains, replies, and attachments. Optional temporary SMS verification sessions. Both will use the same workspace controls.
REST API / TypeScript / Python / CLI / MCP
Communications infrastructure for AI agents
Give your AI agents
a way to reach people.
We're building dedicated email inboxes and SMS verification for AI agents. Phone numbers and calls are next, with permissions and budgets you control.
In development. Email and SMS verification first; texting and calls next.
Initial release
An email inbox for each AI agent.
Give an agent a dedicated email address. It can read incoming messages, send replies, and keep attachments with the conversation.
Hosted inboxes and custom domains are planned for the first release.
See what we're buildingWorkspace
Customer operations
Inbox 1
Sent
Drafts
JDJust now
Jordan Davis
Customer
Can we move our delivery to Friday?
Hi, our team will be out of the office tomorrow. Could you check whether Friday delivery is possible?
Proposed reply for owner review
Hi Jordan, I'll check with the delivery team and get back to you with the available options.
Conversation stays with the agent's inbox
Initial release
SMS verification without the manual handoff.
Let your agent request a temporary number for a supported service, check the price, and read the verification code when it arrives.
Availability depends on the service, country, and provider. Temporary sessions are not permanent phone numbers.
See what we're buildingDestination
Owner-authorized service
Number type
Temporary session
Quote
Allocate
Receive
Code available
••• •••
Reading a code requires permission. Receiving it does not guarantee that the destination service will accept it.
On the roadmap
A phone number your agent can use.
A supplier replies by text. A delivery team needs a call. We plan to give agents persistent phone numbers for those conversations.
Persistent numbers and two-way SMS come after the first release. Voice calls follow. These tools are still on the roadmap.
See what we're buildingVendor coordination
RoadmapFriday works. Please confirm the delivery window.
Thanks. I'll check the time with the team and confirm here.
Continue by phone
Voice calls are planned after email and SMS.
Initial release
Connect through an API or MCP.
Keep the agent and model you already use. Our planned API and hosted Model Context Protocol (MCP) server will let you assign inboxes and permissions to it.
REST, SDKs, CLI, webhooks, and hosted MCP are planned interfaces. The API is not live yet.
See what we're buildingAn example of the intended agent workflow
agent Read the latest customer message
tool Fetch from the assigned inbox
agent Draft a reply with delivery options
policy Check send permission and budget
tool Send the authorized reply
Check permissions before sending.
API requests and MCP tools will follow the same workspace permissions. An agent cannot grant itself more access.
REST API
TypeScript & Python
Signed webhooks
Hosted MCP
One API for your agent's
email and SMS.
Give your agent communications tools without running a mail server or writing a separate integration for every SMS provider.
Give every inbox a clear owner.
We're building one workspace for agent inboxes and verification sessions. Assign each resource to an agent, scope its credentials, and track its usage.
Explore the roadmapPLANNED WORKFLOW
agent / communications
→ Receive a customer message
→ Check assigned inbox permissions
→ Draft a reply with your chosen model
→ Apply owner policy before sending
Agent inbox Example
Re: Friday delivery
I'll check with the delivery team and confirm the available time.
Owner policy checked
Read the message. Check access. Send the reply.
Your agent decides how to respond. Oricin will manage the inbox and delivery, checking permissions before a message goes out.
Planned communications flow
Your agent
Your chosen model
Oricin
Access & spend controls
Email inboxes
Events & SMS
The API, SDKs, CLI, and MCP tools will share the same resources and permissions. Phone tools will use that foundation too.
Decide what your agents can do.
Sending a message or buying a verification session has a real cost. We're building permissions and spending limits into those actions.
Your agent can act.
You set the limits.
Bring your own agent and model. Decide which inboxes, numbers, and actions it can use, and how much it can spend.
Discuss your workflowScoped permissions
Give each agent the access it needs.
Reading and sending will have separate permissions. Owners can assign specific resources, limit code access, and revoke credentials.
Service and country availability
Check what's supported before you start.
SMS availability depends on the service, country, and provider. Oricin will let you check supported options before requesting a session. We'll publish coverage at launch.
Set a spending ceiling.
Check the price before allocating a verification number. Set a workspace budget and a spending limit for each agent.
Know what happened.
Track requests through operation histories and signed webhooks. You'll be able to see whether a send was accepted or a message was delivered.
Retry a request without sending twice.
Start with an inbox.
Grow into a phone line.
We're starting with email and SMS verification. Persistent numbers and voice calls will build on the same API and permission model.
PRODUCT ROADMAP01 / 03
Workspace
Customer operations
Inbox 1
Sent
Drafts
JDJust now
Jordan Davis
Customer
Can we move our delivery to Friday?
Hi, our team will be out of the office tomorrow. Could you check whether Friday delivery is possible?
Proposed reply for owner review
Hi Jordan, I'll check with the delivery team and get back to you with the available options.
Conversation stays with the agent's inbox
Product concept. Oricin is in development.
02
Planned expansion
Numbers & two-way SMS
Phone numbers for AI agents that need to send and receive ordinary texts. These will be separate from temporary verification numbers. Connections to existing Gmail, Microsoft, and Yandex inboxes are also planned.
Persistent numbers / Text conversations / Connected inboxes
03
Further ahead
Voice conversations
Inbound and outbound phone calls for AI agents. We plan to connect your chosen model with speech services, with controls for call permissions and human handoff.
Phone calls / Speech services / Human handoff
Oricin is in development. Pricing, supported routes, and launch dates will be shared before access opens.
A few things
to know.
What we're building, what's coming later, and where things stand today.
What is Oricin?
Oricin is communications infrastructure for AI agents. We are starting with dedicated email inboxes and temporary SMS verification through one API. Persistent phone numbers, two-way texting, and calls are planned next.
Can I use it today?
Oricin is still in development. You can email the founder to discuss your workflow and early access. The previews show product concepts; they are not connected to a live service.
Does Oricin provide the agent or model?
Bring your own agent and model, including Claude. We plan to provide a REST API, TypeScript and Python SDKs, a CLI, signed webhooks, and a hosted Model Context Protocol (MCP) server. Oricin will handle the communications resources.
What will be included in the first release?
The initial release focuses on independent hosted email inboxes and optional temporary, service-specific SMS verification sessions. Persistent phone numbers, ordinary two-way SMS, and voice calls are planned separately. There is no announced launch date yet.
Will agents have unrestricted access?
Owners will choose which resources an agent can access and whether it can read or send messages. The design also includes spending limits, revocable credentials, and approval workflows. A message received from someone else will not grant an agent new permissions.
Are temporary verification numbers permanent phone numbers?
No. Verification sessions are temporary and depend on the selected service, country, and provider. They are not permanent recovery numbers, and receiving a code does not guarantee that another service will accept it. Persistent numbers will be a separate product.
What will it cost?
Pricing has not been announced. We plan to charge a subscription for hosted email and use prepaid credits for verification sessions. Prices, limits, and supported services will be published before paid access opens.
Building an agent that
needs to reach people?
I'm Alper, the founder of ORICIN. If your agent needs an inbox or a phone number, I'd like to hear what you're building.
Email the founderOpens your email app. No signup required.