For developers
Everything open
that can be open.
Open specifications, MCP manifests and OAuth discovery. Whatever an agent or an application needs in order to talk to SIMOSphere AI lives on the platform addresses api.simosphereai.com and onboarding.simosphereai.com. This page lists only what actually answered on August 9, 2026.
Specifications and manifests
Six addresses, all readable without authentication. They do not live under simosphereai.com but at the gateway and at registration, because that is where the API runs and where its description is generated. Every row was fetched on August 9, 2026.
| Resource | What it is for |
|---|---|
api.simosphereai.com/openapi.json | The complete interface description in OpenAPI 3.1. It is generated at gateway startup from the routes actually mounted, so it cannot fall behind the running service. |
onboarding.simosphereai.com/.well-known/mcp/manifest.json | Manifest for the Model Context Protocol, with tools, input schemas and the address where a key is requested. |
onboarding.simosphereai.com/.well-known/mcp/server-card.json | Server card of the MCP service, used for discovery: transport, server URL, authentication scheme, version. |
api.simosphereai.com/.well-known/oauth-protected-resource | Protected resource discovery per RFC 9728, listing the three scopes read, write and admin. |
api.simosphereai.com/.well-known/http-message-signatures-directory | Directory for signed requests per RFC 9421. It answers but carries no key yet: the list is deliberately empty while the specification is still in flux. |
onboarding.simosphereai.com/.well-known/api-catalog | Catalog of interfaces per RFC 9727. It points to the description and the documentation of the gateway. |
Read-only endpoints
Five fetches without a key. Four of them are served by this site itself, the fifth by the platform gateway.
| Endpoint | What comes back |
|---|---|
GET /llms.txt | A guide for answer engines: positioning, the pages that carry the substance, and the questions people actually ask, in both languages. |
GET /llms-full.txt | The same information at length, written for a single fetch rather than for following links. |
GET /sitemap.xml | Every indexable address in both language versions, with the reciprocal language links. |
GET /robots.txt | Rules for search engines and answer engines, with a pointer to the sitemap. |
GET api.simosphereai.com/health | State of the gateway as JSON with a status field and a timestamp. Readable without authentication, including from your own monitoring. |
Access, signatures and limits
The specifications and manifests above need no authentication. Anything that moves data does: the API at api.simosphereai.com uses OAuth 2.0 with authorization code and PKCE plus bearer tokens. Discovery runs through /.well-known/oauth-protected-resource per RFC 9728, and you request a key through registration at onboarding.simosphereai.com.
Verified agents will be able to sign their requests per RFC 9421. The directory already answers but deliberately carries no key while the specification is unsettled. If you depend on it today, write to [email protected].
The public addresses are governed by Cloudflare's default per-address limits. The platform API returns X-RateLimit-Limit, X-RateLimit-Remaining and Retry-After per tier.
The MCP service and its tools
The service sits at https://api.simosphereai.com/mcp and speaks JSON-RPC 2.0 over streamable HTTP. A call without a bearer token is rejected with 401, which is also the simplest probe for whether the address is reachable at all.
Which tools the service carries is stated in the server card and the manifest, and deliberately not in this paragraph, so that the two cannot drift apart. On August 9, 2026 there were five: chat_completion and embeddings with OpenAI-compatible schemas, document_render for PDF and DOCX, plus translate and web_search.
You obtain a key through registration at onboarding.simosphereai.com. It belongs in an environment variable and not in source code, not even temporarily.
curl -X POST https://api.simosphereai.com/mcp \
-H "Authorization: Bearer sk_live_XXXXXXXX" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Roadmap and what is still coming
Announced here means: under way, not yet available. Anything finished sits in the two tables above rather than in this list. The first five items were listed as links on this page until August 9, 2026 and returned 404; they now sit where they belong.
- Separate tool manifests for the public and the protected surface, /.well-known/mcp/marketing.json and /.well-known/mcp/platform.json.
- Index of agent skills at /.well-known/agent-skills/index.json.
- Batching of several JSON-RPC requests into one round trip.
- Machine-readable versions of the offering and consulting details as dedicated endpoints.
- Index of structured data at /schemamap.xml, following the NLWeb proposal.
- Public npm package @simosphere/sdk-js, generated from the OpenAPI description.
- Public PyPI package simosphere-sdk.
- Command-line tool simosphere via Homebrew.
- Verified integration into ChatGPT, Claude and Gemini.
- Listings in the MCP registries mcp.run, mcphub.io and Smithery.
Contact the engine room
- Engineering: [email protected]
- Security: [email protected]
- Everything else: Contact page
SIMO GmbH · Wuerzburger Strasse 152 · 63743 Aschaffenburg · Germany · HRB 15769