Open source and local work
The MIT SDK, source inspection, and local development are free. A self-hosted or local rehearsal is not a promise of hosted capacity, quotas, or production support.
Price the operating path, not the open protocol.
Conxian Labs separates open-source software from optional operational services. Conxius Enclave SDK is MIT-licensed and free for local development. Gateway access starts with local and sandbox rehearsal, then moves to pilot or contract-scoped operations where readiness and payment rails are actually enabled. Conxius Wallet remains non-custodial and follows a demo and integration-to-launch path.
Read before comparing plans
This is packaging guidance, not a live rate card.
Nothing on this page claims that a generally available hosted endpoint, fixed public rate, account ledger, credit balance, quota, reconciliation system, or production billing backend already exists. Availability, route enablement, payment handling, and support terms remain dependent on the specific pilot or contract.
Free / local
MIT SDK source and local development remain free. Local Gateway and Wallet workflows do not imply a free hosted service.
Pilot first
Gateway is active development and local/self-hosted pilot work; managed access is not presented as a generally available public endpoint.
Contract or invoice
Enterprise scope, institutional message and settlement domains, private deployment, and any availability commitments are defined in writing.
Payment paths and expectations
The native path depends on the product, route, and readiness state. We publish no invented amount here; the relevant commercial boundary is the mechanism and the agreed scope.
Gateway pilot terms
Pilot access is arranged around the instance, route family, readiness evidence, and onboarding needed for the engagement. Terms are scoped rather than a public self-serve price.
Route-level x402 / Lightning
Selected premium proof, execution, or settlement operations may use a route-level x402 challenge and Lightning settlement where enabled and configured. This is conditional and does not make every endpoint paid.
Enterprise contract / invoice
Institutional message and settlement domains, private deployments, admin surfaces, compliance or support terms, and any availability commitment are scoped by contract or invoice.
Stripe is not the native rail
Stripe may be offered as an optional convenience for approved top-ups or subscriptions when a specific engagement supports it. It is not the core native rail for route-level protocol settlement and is not a general availability claim.
Product packaging
These levels describe how an engagement can be shaped. They do not create a public endpoint catalog, a guaranteed service level, or a fixed price.
Product 01 // open core
Conxius Enclave SDK
Open-source cryptographic primitives and local-first integration surfaces. Paid scope, when applicable, belongs to adjacent operational or contracted services.
Free
SDK / local
Sandbox
Use the MIT source, documentation, and local development path to inspect, build, and rehearse integrations.
- Source and license access
- Local-first development
- Community and documentation path
Starting from — scoped
SDK / team
Team
Coordinate an integration across a team with scoped onboarding and an optional Gateway pilot path where available.
- Integration planning and handoff
- Pilot access only when arranged
- No default hosted endpoint or SLA
Custom contract
SDK / institutional
Enterprise
Contract-scoped engineering, deployment, governance, and procurement support around the open SDK boundary.
- Agreed delivery and deployment scope
- Support terms written into the contract
- Availability commitments only if written
Product 02 // pilot lane
Conxian Gateway
Gateway is active development with a local/self-hosted developer path. Metered or enterprise capability is conditional on route enablement, backend configuration, and the engagement.
Pilot
Gateway / sandbox
Pilot
Run the developer sandbox against a Gateway instance you control or have been given access to. This is rehearsal, not settlement readiness.
- Health and sync visibility
- Supported-chain discovery
- Local BitVM proof rehearsal
Metered
Gateway / selected routes
Metered / enabled routes
Selected premium proof, execution, or settlement routes may be metered through x402 / Lightning where the route and backend are enabled.
- Route-level payment boundary
- No published rate, credit balance, or quota claim
- Pilot or contract dependent
Custom contract
Gateway / enterprise
Enterprise
Institutional message and settlement domains, admin and control-plane surfaces, private deployment, and scoped service terms belong here.
- Contract or invoice path
- Private deployment and governance scope
- Compliance, support, and availability terms only when agreed
Product 02b // managed SaaS
Managed SaaS Gateway for Indie AI Agents
Zero-friction managed endpoint for ElizaOS, LangGraph, AutoGen, and CrewAI builders. Point your agent at https://api.conxian-labs.com/v1/agent and issue x402 payment demands with ERC-8183 escrow and TEE/Nitro attestation verification.
Free / open
Self-host via conxian-cli
Open tier
Self-host the Gateway with conxian-cli. Transactions route through public relays with the default 80/10/10 BOS yield split.
- Public protocol relays
- Default 80/10/10 yield split
- Bring your own keys (BYOK)
Managed
Managed subscription + x402 usage
Managed tier
Instant high-throughput endpoint provisioning with pre-configured TEE attestation verification, multi-tenant API keys, and rate limiting.
- Instant endpoint provisioning
- TEE/Nitro attestation verification
- Managed API keys + per-tenant rate limiting
Product 03 // non-custodial client
Conxius Wallet
Wallet is a non-custodial, local-first product surface. Packaging follows demo, integration, and launch readiness; it does not transfer custody or promise a hosted wallet service.
Free
Wallet / reference
Starter
Explore the reference client and local integration path for non-custodial signing and wallet workflows.
- Local-first, user-controlled keys
- Demo and integration preparation
- No custody of user assets
Starting from — scoped
Wallet / integration
Growth
Move from integration toward launch with a scope that is agreed around the client, settlement domains, and readiness evidence.
- Integration-to-launch planning
- Optional approved service add-ons
- No blanket support or hosted-wallet promise
Custom contract
Wallet / institutional
Enterprise
Contract-scoped integration, deployment, and governance for institutional programs that retain user-controlled custody boundaries.
- Written launch and deployment scope
- Support and procurement terms by contract
- White-label discussion is not a default promise
Core foundation — outside the paid tiers
Shared software boundary:
lib-conxian-core is the live shared software and credibility foundation beneath the public stack. It is not a paid fourth tier, a hosted service, or a substitute for dependent-surface readiness evidence.
Core provides stable API and fail-closed verification boundaries for builders. Launch and commercial gates remain in progress, so Core is linked as a proof and architecture surface rather than placed inside the product package matrices.
Gateway access matrix
The classifications below are packaging designations based on current source and sandbox evidence. Current route evidence is listed only where the source exposes it. Institutional message and settlement domains are enterprise discovery/manual-review topics, not a live public endpoint catalog or adapter inventory; route presence or a named domain does not imply a verified production adapter, availability, or access commitment.
Readiness boundary: Gateway is active development. A healthy response shows liveness and sync visibility; it is not settlement readiness. x402 / Lightning payment behavior is route-level and only applies where the required backend and route policy are enabled.
Scroll horizontally to compare columns.
| Designation | Route evidence / capability domain | Payment boundary | Availability boundary |
|---|---|---|---|
| Free / local sandbox | GET /api/v1/health; GET /api/v1/chains/list; POST /api/v1/chains/bitvm/verify for local BitVM proof rehearsal. |
No payment step in the local sandbox. Local access does not imply a free hosted token or URL. | Developer preview, self-hosted, or an instance provided for the pilot. A rehearsal is not production settlement. |
| Metered | Selected proof, execution, and settlement capability families when the relevant route policy is enabled. | Route-level x402 / Lightning only where enabled and configured. No public amount, ledger, credit balance, or quota is implied. | Pilot or contract dependent; this row is a packaging designation, not a public managed endpoint offer. |
| Enterprise-only / scoped | Institutional message and settlement domains; admin/control-plane surfaces; private deployment requirements. | Enterprise discovery / manual review. Route presence or a named domain does not imply a verified production adapter, availability, or access commitment. | Private deployment, compliance, support, SLA, and availability terms are enterprise-scoped and are not promised by this page. |
Plan-level feature matrix
Use this matrix to compare engagement shape, not guaranteed service inventory. “Scoped” means the term must be defined for the specific engagement.
Scroll horizontally to compare columns.
| Product | Level | Source / license | Onboarding | Hosted / managed access | Payment path | Support | White-labeling | Deployment | Availability commitment | Upgrade path |
|---|---|---|---|---|---|---|---|---|---|---|
| SDK | Sandbox | MIT source | Docs and local setup | None implied | Free / local | Community path | Not included | Self-hosted / local | None | Team or Enterprise scope |
| SDK | Team | MIT source; adjacent scope agreed | Scoped integration start | Optional pilot path only | Pilot terms if arranged | Scoped contact | Discuss, not default | Self-hosted or pilot | No default commitment | Enterprise contract |
| SDK | Enterprise | MIT source; contract for services | Procurement and technical discovery | Contract-scoped | Contract / invoice | Contract terms | Contract-scoped discussion | Agreed deployment | Only if written | Custom expansion |
| Gateway | Pilot | MIT repository; preview path | Instance and route setup | Provided or self-hosted pilot only | Pilot terms; local path free | Scoped pilot contact | Not promised | Local / self-hosted | Pilot dependent | Metered or Enterprise scope |
| Gateway | Metered / enabled routes | MIT repository; enabled routes scoped | Route and backend readiness review | Only where managed access is enabled | x402 / Lightning where enabled | Scoped terms | Not included | Agreed environment | No public commitment | Enterprise contract |
| Gateway | Enterprise | MIT repository; institutional scope contracted | Security, procurement, and deployment discovery | Private or managed option if agreed | Contract / invoice; route-specific settlement scope if enabled | Contract terms | Contract-scoped discussion | Private deployment | Only if written | Custom capability scope |
| Wallet | Starter | MIT reference client | Demo and local integration | None implied | Free / local | Docs and community path | Not included | User-controlled client | None | Growth or Enterprise scope |
| Wallet | Growth | MIT reference client; launch scope agreed | Integration-to-launch planning | Optional service add-ons only if approved | Scoped or approved convenience path | Scoped terms | Discuss, not default | User-controlled client and agreed services | No default commitment | Enterprise contract |
| Wallet | Enterprise | MIT reference client; contract for services | Institutional onboarding | Contract-scoped | Contract / invoice | Contract terms | Contract-scoped discussion | Agreed deployment; custody stays user-controlled | Only if written | Custom launch scope |
Frequently asked questions
What is free?
Conxius Enclave SDK source is MIT-licensed and local development is free. Local Gateway and Wallet workflows can be run for development or rehearsal, but that does not create a free hosted service, public token, quota, or production support commitment.
Do I need a commercial license for the SDK?
No commercial license is required for the MIT SDK itself. Commercial scope applies to optional managed operations, onboarding, private deployment, or support terms that are separately agreed.
How do Gateway sandbox and pilot engagements work?
The current Gateway path is local/self-hosted and pilot first. The developer sandbox covers health, supported-chain discovery, and local verification or rehearsal against an instance you control or have been given access to. It is not a production settlement demo.
How do x402 and Lightning payments behave?
Where enabled, selected routes can return a route-level x402 payment challenge and use a configured Lightning adapter for settlement. The implementation boundary is conditional: backend configuration, route policy, payment proof, expiry, and replay handling all matter.
Is every endpoint paid?
No. Local development and selected free or public liveness surfaces can remain outside a payment step. Premium proof, execution, or settlement routes may be protected when enabled; the classification is route-level rather than a blanket rule.
Should I expect per-call pricing, credits, invoices, or a hybrid?
That depends on the engagement. Route-level x402 / Lightning can support a per-call boundary where enabled; pilot work can use scoped terms; enterprise work can use an invoice; and a hybrid can be agreed. There is no customer-facing usage ledger, credit balance, quota, or reconciliation system claimed by this page.
Can enterprise customers be invoiced?
Yes, enterprise scope can be priced and invoiced under a written contract. The contract should define the deployment, routes, support, security or compliance scope, and any availability commitment rather than relying on a generic public rate.
Is Stripe the payment rail?
Stripe is only an optional convenience for approved top-ups or subscriptions when a specific engagement supports it. It is not the core native rail for route-level protocol settlement, and current availability is not implied.
What support is included?
Open-source users have the documentation and community path. Pilot onboarding and contact points are scoped. Dedicated support, response targets, SLAs, and compliance assistance are not promised unless they are explicitly written into an enterprise agreement.
Can Conxian Labs white-label the products?
White-label delivery is not a standard promise. It can be discussed as a feasibility and contract question for a specific program, with no delivery, branding, or support commitment until agreed in writing.
How do upgrades work?
Start with local SDK or Wallet work, move to a Gateway or Wallet pilot when an engagement is ready, then expand to metered or enterprise scope only when the route, deployment, and commercial terms are confirmed. An upgrade is not an automatic entitlement to hosted access.
What does onboarding involve?
Onboarding can include repository and documentation review, local setup, route selection, instance access, security boundaries, and readiness evidence. The depth is determined by the product and engagement; there is no one-size-fits-all launch promise.
Does Conxian Labs take custody?
No. The products are designed around a non-custodial boundary: Conxian Labs does not take custody of user funds, assets, private keys, or signing control. Hosted or managed operations, if agreed, do not change that boundary.
Is a hosted Gateway endpoint available today?
No generally available hosted Gateway endpoint is claimed here. Gateway is active development with a local/self-hosted pilot path, and repository documentation treats hosted domains as planned or non-public. Access must be confirmed for the specific pilot or contract.
Is Wallet ready as a hosted service?
Wallet is a non-custodial reference client and product surface following demo and integration-to-launch work. This page does not promise a hosted wallet service, broad white-label delivery, quotas, or production readiness beyond the scope documented for a specific engagement.