This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
On a security or compliance team? Email info@apievangelist.com with security in the subject line and you will get a person, not a form. We will tell you exactly which public URLs this profile was built from so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
Totogi LLC is an Austin, Texas based vertical AI and BSS software vendor that builds telecom operator software natively on the public cloud (AWS). Its two products are the Totogi Ontology (formerly BSS Magic), a machine-readable semantic layer that sits above a carrier's existing BSS, OSS, core, and network systems so AI agents can reason and act across them, and Totogi Charging-as-a-Service, a multi-tenant, serverless 5G Standalone converged charging system with built-in policy control that integrates over the 4G/5G NSA Sy (PCRF) and 5G SA N28 (PCF) interfaces. Totogi sells to communications service providers, MNOs, MVNOs, and MVNEs — it does not own spectrum and it does not sell to developers directly.
APIs.json: https://raw.githubusercontent.com/api-evangelist/totogi/refs/heads/main/apis.yml
- Telecommunications
- United States
- BSS
- OSS
- Charging
- Messaging
- SMS
- A2P
- 5G
- TM Forum
- Standards
- Network Vendor
- Vertical AI
- Created: 2026-07-25
- Modified: 2026-07-25
Whoosh! is Totogi's Application-to-Person (A2P) messaging API, launched in September 2023 and positioned as a drop-in replacement for Twilio's A2P APIs that network operators can resell to keep enterprise messaging traffic and revenue on their own network. The REST surface deliberately mirrors Twilio's 2010-04-01 account/resource shape, authenticates with HTTP Basic using an Account SID and Auth Token, and pushes delivery status back through a StatusCallback webhook. Quickstart documentation is public and un-gated; the console that issues credentials is not, and there is no self-serve signup.
- Human URL: https://docs.whoosh.totogi.solutions
- Base URL:
https://api.whoosh.totogi.solutions/2010-04-01/Accounts/
- Messaging
- SMS
- A2P
- CPaaS
- Webhooks
- Documentation
- API Reference
- Webhook / status callback docs
- Console
- Node.js SDK —
whoosh-smson npm - Python SDK —
WhooshSmson PyPI - Ruby SDK —
whoosh-rubyon RubyGems - Java SDK — GitHub releases
- Launch announcement
A serverless, multi-tenant 5G Standalone and 5G Advanced converged charging system delivered as SaaS on AWS, with built-in policy control and a single account management API across tenants. Totogi's BSS surface is built on TM Forum Open APIs, for which Totogi holds Platinum Conformance Certification across 31 certified Open APIs. The product's API reference is published on a Redocly-hosted portal that returns a "Log in with Redocly" wall to anonymous visitors — no specification, endpoint list, or base URL is publicly retrievable.
- Human URL: https://totogi.com/ai-native-charging/
- Charging
- BSS
- 5G
- TM Forum
- Policy Control
- Documentation
- API Reference (login wall)
- Product updates
- TM Forum Open API Conformance
- AWS Marketplace listing
Totogi's developer surface is split, and both halves are findings.
The platform documentation is a login wall. The first-party API reference at https://docs.totogi.solutions is a Redocly-hosted portal that returns HTTP 200 with a "Log in with Redocly" page to anonymous visitors. Every spec-shaped path probed on that host returns the same login HTML. developer., developers., docs., api., console., dev., and sandbox. under totogi.com do not resolve at all, and totogi.com/developer, /api, and /docs return 404. There is no self-serve signup and no downloadable OpenAPI anywhere.
Whoosh is the one open surface. The Whoosh docs are public, the API host is live, four helper libraries are published to npm, PyPI, RubyGems, and GitHub Releases, and the webhook contract is documented. But Whoosh is sold through operators to their enterprise customers — Totogi's own launch language is that the telco handles connectivity and sales while Totogi delivers the APIs. Developers reach it via a carrier, not via a signup form.
No CAMARA. There is zero mention of CAMARA, GSMA Open Gateway, or Aduna in Totogi's own canonical AI index (llms.txt, llms-full.txt, facts.json, evidence.json, glossary.json, case-studies.json) or anywhere on the site. This is not a press-release-only posture — there is no press release either. Totogi's standards alignment is TM Forum and 3GPP. glossary.json defines Network Exposure Function as a term, but Totogi makes no claim to operate or expose one.
TM Forum is where the certification is. Totogi announced Platinum Open API Conformance Certification and the #1 spot on TM Forum's Open API Certification Leaderboard in September 2021, reaching Platinum in four months and finishing the month with 31 certified Open APIs. The individual TMF numbers are not published by Totogi, and the TM Forum conformance directory returns HTTP 403 to anonymous fetch, so the itemized list could not be enumerated. Totogi also sells certification acceleration as an outcome: a published case study describes CloudSense certifying 13 TM Forum Open APIs in 30 days with the Totogi Ontology.
Machine-readable about itself, gated about its APIs. Totogi publishes llms.txt, llms-full.txt, and four canonical "AI Index" JSON documents linked from its footer, and robots.txt explicitly welcomes GPTBot, ClaudeBot, PerplexityBot, CCBot, and friends. A telecom vendor that machine-readably publishes its own facts and evidence while keeping its API reference behind a Redocly login is a precise illustration of the sector split.