Every reader gets the whole platform.
Read Praxis in the workbench, over the API or through AI agents, in the hosted service or in your own infrastructure. Every path reads the same models and the same data.
Every way in reads the same API.
Workbench
For analysts: sign in through the host application, and the workbench reads the API with your session.
- Every module, the globe, the time machine and the command bar
- Alerts and watchlists that follow you across devices
- Briefs and dossiers as Markdown
HTTP API
For your systems: authenticate with access tokens from the deployment's identity provider, as a user or as a service.
- An OpenAPI 3.1 document to generate clients from
- Every read model, with its provenance
- Conditional reads and stable error codes
Model Context Protocol
For AI agents: the same credentials as the API, with every read operation offered as a read-only tool.
- Tools generated from the API's own definition
- Answers pinned to a date and a revision
- No write access
Dedicated deployment
For your infrastructure: Praxis behind your own gateway and identity provider, with its own PostgreSQL database. Available by agreement.
- Your identity provider issues every token
- Your scheduler, holding a sync-only identity
- Releases rolled out on your schedule
No feature tiers.
Access is scoped by who reads and how, never by which models or sources they may see.
Every model
Every assessment, index, outlook and scenario the methodology computes.
Every source
Every source in the catalog, with its provenance and its state.
Every past state
Every data revision, readable as of any date the data covers.
The full methodology
Every model's procedure, parameters, references and limitations.
From request to first answer.
- 01
Request access
Tell us your use case, your themes and regions, and how your team will read the answers.
- 02
Agree the scope
The identities for people, systems and agents, and for a dedicated deployment, its infrastructure.
- 03
Receive credentials
Workbench sign-in for analysts, and access tokens for your systems and agents.
- 04
Connect
Open the workbench, make your first API request or register the endpoint with your agents.
About access.
Pricing depends on the access paths, the number of people, systems and agents, and the deployment model, so it is agreed with each organization rather than published as a price list.
Any provider that issues signed JSON Web Token access tokens and publishes its keys. In the hosted service, we issue the credentials; in a dedicated deployment, your identity provider does.
No. The Model Context Protocol endpoint accepts the same bearer tokens as the API, with the same capabilities and the same answers.
A PostgreSQL database, a gateway that terminates TLS and limits rates, your identity provider, and a scheduler that holds a sync-only service identity.
Every reader sees every model and source. Teams choose their own themes, regions and actors in the lens, which changes what is shown but never a number.
Choose your path and request access.
Tell us which paths your team needs, and we scope identities, credentials and onboarding with you.