Amdocs
Amdocs is a global technology company providing software and services to communications and media companies worldwide. Its connectX platform is a cloud-native SaaS BSS solution for telecom operators covering customer management, billing, provisioning, and subscription lifecycle. Amdocs also provides MarketONE for digital BSS, NetCracker for OSS network management, and an expanding suite of AI-powered telco solutions built on TM Forum Open APIs.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Amdocs the way a machine reads it — 88 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amdocs scores 52.8/100 (developing), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Amdocs
Each block below is one kind of artifact we hold for Amdocs. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Amdocs MarketONE API
The Amdocs MarketONE API provides digital BSS capabilities for telecoms, supporting catalog management, order management, customer management, and digital service delivery. REST...
Amdocs NetCracker OSS API
The Amdocs NetCracker OSS API provides network inventory management, network provisioning, and service assurance capabilities for telecom operators. REST and SOAP APIs support i...
Amdocs Billing API
Billing and invoice operations
Amdocs Customers API
Customer account management
Amdocs Products API
Product catalog management
Amdocs Subscriptions API
Subscription lifecycle management
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Amdocs connectX BSS API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Amdocs Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Amdocs Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Amdocs Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
TM Forum Open API Compliance
All connectX APIs comply with TM Forum Open API standards, enabling fast integration with third-party systems and reducing customization requirements.
AI-Native Capabilities
GenAI-powered platform capabilities including AI-driven customer journeys, predictive analytics, and automated decision making for telco operations.
Cloud-Native SaaS Architecture
Serverless microservices architecture deployed on AWS providing elastic scalability, local data residency compliance, and rapid deployment for MVNOs and telcos.
eSIM Management
Built-in eSIM lifecycle management enabling telcos and MVNOs to support digital SIM provisioning without physical SIM cards.
Omnichannel Customer Experience
Pre-built customer journeys spanning mobile apps, web self-service, and multi-channel support for consumer and business segments.
MVNO and MVNE Support
End-to-end MVNO and MVNE capabilities including wireless prepaid, postpaid, and B2C solutions with rapid market launch support.
Catalog and Order Management
Flexible product catalog management for bundling connectivity with digital services, plus end-to-end order management across consumer, business, and enterprise segments.
Revenue Management
Converged billing, revenue assurance, and monetization capabilities supporting current and emerging revenue models including subscription and usage-based billing.
Scroll within the panel for all 8 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Amdocs connectX BSS Event API
The Amdocs connectX BSS Event API delivers real-time event notifications for telecom BSS operations including customer lifecycle events, subscription changes, billing events, an...
ASYNCAPISemantic Vocabularies 3
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 15
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Amdocs Customer
JSON SCHEMAAddress
JSON SCHEMACustomerList
JSON SCHEMACustomerRequest
JSON SCHEMACustomer
JSON SCHEMACustomerUpdate
JSON SCHEMAInvoiceLineItem
JSON SCHEMAInvoiceList
JSON SCHEMAInvoice
JSON SCHEMAPagination
JSON SCHEMAProductList
JSON SCHEMAProduct
JSON SCHEMASubscriptionList
JSON SCHEMASubscriptionRequest
JSON SCHEMASubscription
JSON SCHEMAScroll within the panel for all 15 ·
JSON Structure 15
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Amdocs Customer Structure
JSON STRUCTUREConnectx Address Structure
JSON STRUCTUREConnectx Customer List Structure
JSON STRUCTUREConnectx Customer Request Structure
JSON STRUCTUREConnectx Customer Structure
JSON STRUCTUREConnectx Customer Update Structure
JSON STRUCTUREConnectx Invoice Line Item Structure
JSON STRUCTUREConnectx Invoice List Structure
JSON STRUCTUREConnectx Invoice Structure
JSON STRUCTUREConnectx Pagination Structure
JSON STRUCTUREConnectx Product List Structure
JSON STRUCTUREConnectx Product Structure
JSON STRUCTUREConnectx Subscription List Structure
JSON STRUCTUREConnectx Subscription Request Structure
JSON STRUCTUREConnectx Subscription Structure
JSON STRUCTUREScroll within the panel for all 15 ·
Examples 15
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Amdocs Customer Example
EXAMPLEConnectx Address Example
EXAMPLEConnectx Customer Example
EXAMPLEConnectx Invoice Example
EXAMPLEConnectx Pagination Example
EXAMPLEConnectx Product Example
EXAMPLEScroll within the panel for all 15 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
MVNO Launch
Rapidly launch new MVNO brands with pre-integrated telco-in-a-box capabilities including customer management, billing, and digital channels.
BSS Digital Transformation
Migrate from legacy BSS to cloud-native SaaS BSS with TM Forum Open API compliance and pre-built integrations for telco digital transformation.
5G Monetization
Launch and monetize 5G services with flexible catalog management, usage-based billing, and analytics for network slicing and IoT.
Customer Self-Service
Deploy omnichannel self-service portals and mobile apps with pre-built customer journeys for account management, plan changes, and billing.
Gen Z Mobile Services
Launch fully customizable mobile plans enabling subscribers to configure data, calls, texts, and plan length via AI-powered apps.
IoT Service Management
Manage IoT connectivity, device onboarding, and usage-based billing for enterprise IoT deployments across telecom networks.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
AWS
connectX is powered by Amazon Web Services providing cloud infrastructure, elastic scalability, and global reach.
TM Forum Open APIs
Full compliance with TM Forum Open API standards enabling plug-and-play integration with ecosystem partners and third-party systems.
Microsoft
Customer Engagement Platform partnership with Microsoft for AI-driven customer interactions and analytics.
Network Management Systems
Integration with multi-vendor network management systems and OSS platforms via NetCracker APIs.
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
connectX
All-in-one SaaS BSS platform for telcos and MVNOs with AI-powered customer management, billing, and monetization capabilities.
MarketONE
Digital BSS platform for managing and monetizing subscriptions with integrated digital partners and omnichannel delivery.
Amdocs Networks
Telco cloud transformation solutions for 5G, fiber, and IoT network deployment and optimization.
Digital Financial Services Platform
Mobile wallet and financial services enablement for telco operators entering digital banking and fintech markets.
Resources
Every other property we hold for Amdocs — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/amdocs · machine-readable index on apis.io