Capability / APIs & infrastructure · API, SDK, keys, metering
We build it.We run it.
We design the API, write its documentation and SDK, issue the keys, meter every call and run the service. Choose what your product needs and watch its backend come together.
Fig. 05 — Service composition
Six service bundles, one real product, or your own mix.
Choose a bundle, or switch parts on and off.
The backend, built and run.
We build the services behind a product and run them: an API with documentation, keys for each customer, a count of every call, limits and billing, and the SDK a developer uses to call it. Services are made to be combined, so a product starts from a bundle instead of from nothing.
Stop rebuilding the same backend.
Most of a new product's backend has been built before: sign-in, keys, metering, billing, search, memory, speech. Rebuilding it for every product is slow and each rebuild has new faults. A team that only delivers a frontend leaves the hard part to you.
A catalogue of services.
The MayaClerk developer API is public today. The rest of the platform runs on our own machines and is not open for public sign-up.
- MayaClerk developer API
Live - Lets other software search U.S. court opinions and fetch a full opinion over HTTP. Documented and versioned, with self-serve keys that are shown once and stored only as a hash.
- Key console
Built and tested - Create, name and revoke customer keys. One key works on every service; a revoked key stops working everywhere within about a minute.
- Accounts and metering
Built and tested - A workspace per customer, plans, a count of every call per key, a free monthly allowance, a prepaid balance and invoices by month. Refuses a call when the balance is empty, the key is revoked or the rate limit is passed.
- Model gateway
Built and tested - One API in front of several AI model providers, using the customer's own provider keys, with streamed answers and usage and cost recorded per key.
- Voice API and studio
Built and tested - Text to speech, speech to text, streamed speech and a two-way spoken conversation that can be interrupted. Comes with an embeddable voice component.
- Personality API
Built and tested - Create, version, compare, roll back, export and import an assistant's personality.
- Knowledge service
Built and tested - Upload documents into collections, search them by meaning and by exact words, and answer with cited passages.
- Companion API
Built and tested - Build an assistant from a personality, a model, optional memory and documents, and talk to it through an API, a hosted chat page or a chat box dropped into any page. Each customer's data is separate.
- Memory service
Built and tested - Long-term memory for assistants: propose, recall, rate, fade, correct, forget and export, with consent per person. Every request is signed and each site, user and companion has its own store.
- SDK, documentation and playground
Built and tested - A typed JavaScript SDK with a client for each service, a documentation page per service, and a page to try real requests without exposing a key.
Nine services sit behind one SDK, with more than 100 API routes between them. Across the platform's eleven latest deliveries, 200 acceptance criteria passed twice, once in independent review and once at final acceptance, with no findings. A live end-to-end chain of nine steps, from sign-up to a metered call, passed nine of nine.
The six bundles.
- Chatbot
- A branded chatbot with a personality and a chosen model, metered through the gateway.
- Voice AI
- Talk to a companion: speech to text, the companion's turn, text to speech.
- Personal AI
- A companion that remembers: personality plus signed long-term memory.
- Digital human
- An embodied companion: avatar, voice and a 3D surface around it.
- Knowledge assistant
- A companion that answers from your documents and cites them.
- Custom software
- Accounts, keys, metering and the model gateway as the base of a product of your own.
Your API, your bundle, your name.
The API itself: we design it around your data and your product. The bundle: which services your product needs. The plans, limits and prices your customers see. The model providers, with your own keys. Your name on the documentation, the SDK and the embeddable components.
Hosted by us, or on your servers.
Hosted and run by us, with keys, metering and invoices for your customers. Or deployed on your own servers or cloud. Either way your developers get the documentation, the SDK and a playground.
See it assemble.
The figure above. MayaClerk's public developer documentation at mayaclerk.com/api-docs.