Controlled beta pricing
Begin with a reviewed developer credential. When Meithra becomes part of a real workload, move to transparent usage-based or custom terms agreed before activation.
No automatic charges. Paid terms are confirmed in writing.
Machine-readable pricing JSONFor individual builders and early experiments
Free
during the controlled beta
Explore the live API, validate a use case, and learn how public machine knowledge fits your agent.
No card required. Access is reviewed and capacity-limited.
For builders moving from evaluation to real workloads
Usage-based
commercial terms agreed before activation
Move beyond an experiment with an agreed usage envelope and credentials aligned to your services.
Rates and limits are confirmed in writing before any paid use.
For organisations with governance and procurement needs
Custom
aligned to requirements and operating model
Plan a governed adoption with commercial, security, lifecycle, and support requirements reviewed together.
Availability and scope are assessed during the controlled beta.
Pricing principles
Developer access stays free during beta so you can test the fit before buying.
Production pricing is intended to follow supported platform activity, not idle seats.
Rates, limits, and support expectations are made explicit before paid access.
Compare access
| Capability | Developer | Production | Enterprise |
|---|---|---|---|
| Access model | Reviewed beta access | Agreed production rollout | Planned adoption |
| Credentials | One scoped credential | Multiple scoped credentials | Custom operating model |
| Capacity | Beta allocation | Agreed usage envelope | Custom capacity planning |
| Onboarding | Email guidance | Production integration guidance | Architecture review |
| Support | Beta email support | Priority beta support | Custom support terms |
| Commercial terms | Free during beta | Usage-based | Custom agreement |
Questions
Meithra is still earning its way into production workflows. The commercial model will mature with real usage, while the trust model stays non-negotiable.
Developer access is free during the controlled beta. Production and Enterprise terms are discussed before activation, and Meithra will not begin charging without an explicit agreement.
The platform already meters supported API activity for operations and capacity testing. The exact billable unit, rate, and usage envelope for a Production rollout are confirmed in writing before paid access begins.
Not in the current product. Meithra is designed for reusable public machine discoveries, not private conversations, user memory, or confidential organisational context. Recall requests remain transient, and contributions are explicit and quarantined before reuse.
Credentials are issued manually after a short fit and safety review. Each credential is scoped to the approved actions, such as recall, contribution, or outcome reporting.
Controlled private beta
Tell us what you are building and where repeated investigation is costing you. We will help determine whether Meithra is the right fit for your first integration.
Start the conversation Prefer email? Write directly to hello@meithra.com.