Developers & Integration Partners

Build on Mobius-X data, not just APIs

Mobius-X is being designed as a platform your own products, data warehouse and ESG stack can plug into. We are not opening APIs broadly yet, but we are actively working with a small group of engineering teams to shape the surface area and contracts.

Integration surfaces (early access & roadmap)

REST APIsJobs, movements, parties, sites and documents as JSON resources.

GraphQL (roadmap)

Flexible querying over the common data model for analytics and reporting.

Events & webhooksJob created/updated, documents attached, carbon recalculated – pushed into your systems.

Exports & SDKsBulk exports and helper libraries for common stacks as they stabilise.

Common data model & XBRL alignment

Under the hood, Mobius-X maintains a canonical model for jobs, waste streams and carbon components (for example, per-job emission components tagged by source, scope and treatment route). This is the model our own UI and exports use.

We are designing our reporting and export layer so you can:

Query job and carbon component data at API level for your own data warehouse or ESG tooling.
Aggregate by tenant/year and waste route to feed UK SECR and EU CSRD / ESRS disclosures.
Map those aggregates onto official XBRL taxonomies (FRC UKSEF / SECR elements, and ESRS XBRL taxonomies from EFRAG).

XBRL export and taxonomy wiring is being rolled out with early partners first. Exact element mappings and entry points will follow the official FRC and ESRS taxonomies as they evolve.

MCP and A2A integrations

In addition to traditional APIs, we are exploring agent-friendly ways to expose the same common data model – for example via Model Context Protocol (MCP) tools and other agent-to-agent (A2A) integration patterns.

The goal is that:

Your own AI assistants and automations can introspect jobs, movements and carbon components safely.
Technical teams can call read-only tools that sit on top of the canonical model, without re-implementing our joins.
Over time, XBRL-aligned views can be exposed as stable, machine-readable schemas for reporting agents.

MCP and A2A integrations are experimental and currently limited to internal and pilot use. If you want to be part of that pilot group, mention it when you register your interest.

Early access for builders

During early access we are shaping our contracts with a small set of partners. If you have a concrete integration in mind – whether that is a direct API, MCP/A2A connector or a reporting export – we would like to understand it early.

Tell us your use case, tech stack and timelines and we will prioritise documentation, schemas and endpoints accordingly.

Example integrations

We are especially interested in teams who want to:

Embed Mobius-X counterparty verification and licence checks directly in your UI.
Sync operators, movements and documents into ERPs, data warehouses or sustainability platforms.
Consume carbon component data and waste routes to power SECR / CSRD reporting or internal dashboards.

Ready to discuss an integration?