Other vendors will sell you their AI agents. With PortaOne, you choose the AI – including an open-weight model running on your own hardware, in your own country.
It reads the documentation, works on behalf of you, your resellers and your customers, and answers questions across years of your own data. All of it under permissions you set, in a log you can search.
Staff, resellers, and customers keep coming back to your team for answers and routine changes.
Connect the AI you already use to PortaBilling and PortaSwitch, under the access controls you already run.
Once connected to PortaBilling, an AI agent can do more than answer generic questions. It can work with live billing data, customer accounts, products, and services within the permissions you give it.
“Why is this customer’s invoice €42 higher than last month?”
The agent checks the account, usage, and invoice together, then explains the difference without making your support team jump between screens.
“Add an extension for our new starter.”
Your business customers can change their own service or resolve billing questions through an agent you provide, constrained to their own account.
“Which of my customers are close to their limit this month?”
Resellers and distributors can query their own customer base directly instead of raising a ticket with your team.
“Draft a product for customers still on the 2019 plan.”
The agent can prepare a configuration from what already exists in your catalogue, ready for a person to review before anything goes live.
The MCP server is one part of a broader set of AI capabilities already available around PortaBilling and PortaSwitch.
Administrators can ask questions directly in the PortaBilling interface and get answers based on the documentation for the release they are running.
Your AI can read PortaOne documentation, release notes, and API specifications through the MCP server, without accessing customer data.
When standard reports are not enough, historical billing data can be made available for deeper analysis. This lets your AI answer questions across longer periods without relying on manual SQL work or stitching reports together.
MCP is the open standard AI agents use to work with external systems. The connection is open, not proprietary to PortaOne.
A user makes a request in ChatGPT, Claude, Microsoft Copilot, GLM, Kimi, Deepseek, etc. or an agent your own team built.
PortaOne hosts and maintains the server. The agent sees which PortaBilling tools it can use and can pull in PortaOne documentation when it needs more context.
PortaBilling opens its own login and consent screen. The user logs in and grants access just once, allowing the agent to handle subsequ
Every request runs within the role and permissions you assigned. Every change is recorded in the audit log under the agent’s own identity.
In PortaBilling, an AI agent is onboarded like a person. It gets its own username, password, role, and access controls, so you decide exactly what it can see and what it can change.
Choose what the agent can access and whether its permissions are limited to viewing or include modifications.. Roles are available for admin, reseller, customer, account, distributor, and representative users.
Use data masking when an agent needs to work with billing or service information without seeing personal customer details.
All actions are recorded in the audit log, so you can track which agent accessed or modified data.
Update the role to change the agent’s permissions, or disable its user account to stop access completely.
You choose which PortaBilling API tool groups are exposed to each AI agent. Start with the functions it needs for the job, and leave everything else out.
Select the relevant PortaBilling API v2 tool groups for the agent’s role, whether that means customers, accounts, products, services, or billing operations.
If a function you need is not yet available as an MCP tool, you can add it from PortaBilling API v1 instead of waiting for a new product release.
The MCP connection gives the agent access to PortaBilling business functions. It does not give it access to your mobile core and does not grant the AI unrestricted access. Instead, it provides a controlled set of PortaBilling capabilities for a specific agent and job.
PortaOne also lets you package selected AI capabilities as customer-facing services, with your own pricing and rate structure.
Add voice agents to your cloud PBX or SIP trunking offer and charge per minute or as part of a service plan.
Offer automatic transcription for call recordings and voicemail, with the service included in a bundle or billed separately.
Generate spoken IVR messages such as names, codes, or status updates, and include the usage in your own rate card.
Any AI that is compatible with MCP can connect to PortaBilling. This includes commercial assistants like Claude, ChatGPT, and Microsoft Copilot, and equally covers an agent your own team builds. The connection does not know which model is on the other end of it, nor does it care, so model choice remains yours, both now and in the future.
Yes. PortaBilling does not supply a model and does not require one. Inference happens wherever you run it, so an open-weight model on your own servers, or a regional provider your regulator has already accepted, works exactly as a commercial assistant does. The takeaway is simple: a platform that only works with one vendor’s cloud AI becomes obsolete quickly, but PortaBilling is built for long-term flexibility..
No. Two aspects dictate where things run, and you control both. The model runs wherever you run it, so a self-hosted or in-region model never sends a prompt outside your own infrastructure. The MCP server that connects your agent to PortaBilling is hosted by PortaOne in a datacenter you select when you deploy it, normally the one closest to your own installation, and we can activate further locations on request. If you have a residency rule, raise it early, so we can plan exactly where each component will run..
No. PortaOne provisions, hosts, and maintains a dedicated MCP server for you, and it is yours rather than a shared service, so you configure it independently. You point a domain of your own at it, for example mcp.yourcompany.com, and either upload your own TLS certificate or let PortaOne issue one. There is no server for you to run or patch.
An agent reaches PortaBilling through the PortaBilling API and nothing else. You choose which API v2 tool groups it sees, such as customers, products, or services, and you can add individual API v1 methods by name when you need something beyond that. Nothing else on your network is reachable through the MCP server, and your mobile core is untouched.
You onboard an agent the way you onboard a person. It gets its own PortaBilling user account, role, and access controls, with every resource in that role set to restrict, read, or modify. There is no limit on how many users you create, so every agent can have its own configuration.
Because the agent signs in as itself, its work never blends into a staff member’s history. Every change is recorded against the agent’s own name, with the properties it touched and their old and new values. When someone asks who changed a tariff at three in the morning, the answer names the agent. Edit the role and the agent’s reach changes with it. Switch the user off and the agent stops.
Only if you let it. PortaBilling masks personal data per user – both on screen and in API responses. Switch it on for the agent’s user and names, addresses, and contact details come back hidden, so an agent can answer a billing question without ever seeing whose account it is.
Yes. PortaBilling exposes admin, reseller, customer, and account separately, each on its own endpoint with its own selected set of tools, and you enable only the ones you want. A reseller’s agent sees that reseller’s own customers. A customer’s agent sees that customer’s own account. You decide which of the four endpoints to switch on.
PortaOne’s latest updates help service providers improve operational efficiency, enhance service control, and deliver more flexible communication services. In this webinar, we walked through the
How WTL and PortaOne helped One Mobile bring true 5G to Sierra Leone, fast
PortaOne’s latest updates help service providers simplify daily operations, launch new services faster, and stay competitive in their markets. In this webinar, we walked through
AI automation for telecom transforms CSPs, cutting costs and boosting efficiency without coding. Virtual-Call saves 20+ hours weekly using AI tools like Claude and Perplexity
DIY billing scripts for your AI agent delay launches & leak profits. PortaAIM’s API handles usage-based billing, real-time cost tracking, flexible pricing & invoicing.
In this blog story we examine whether AI (and PortaAIM) will take over humanity – plus: the current state of the AI agents landscape,
