Credits & Payments
The platform utilizes a credit-based metering system to track usage and facilitate permissionless access.
Credit System
Usage is metered in Credits. The standard conversion rate is 1 Credit ≈ $0.001.
Operation Costs
| Operation | Cost (Credits) | Description |
|---|---|---|
| Create | 5 | Ingesting and vectorizing a new memory. |
| Search | 2 | Semantic search query against the index. |
| Update | 2 | Modifying existing memory content or metadata. |
| Get | 1 | Retrieving a memory by its specific ID. |
| Delete | 1 | Removing a memory from the index. |
Pay-Per-Use Model
Unlike traditional cloud services that require provisioning servers based on predicted usage, zkStash operates on a true pay-per-use model.
No Idle Costs
You’re only charged for the resources you actively use. There’s no need to over-provision for peak loads or pay for idle capacity during quiet periods. This aligns pricing directly with actual utilization.
Flexibility
Our system scales seamlessly based on your demand:
- Traffic Spikes: Resources scale up automatically to meet demand.
- Quiet Periods: Resources scale down to minimize costs.
Focus on Innovation
Developers can concentrate on building features rather than optimizing infrastructure. The platform handles scaling automatically, allowing you to focus on creating value for your users.
Rate Limits
To ensure fair usage and system stability, we enforce rate limits based on your plan.
| Plan | Requests / Minute | Requests / Hour | Requests / Day |
|---|---|---|---|
| Permissionless (x402) | 10 | 300 | 5000 |
| Starter | 100 | 3000 | 50000 |
| Pro | 500 | 15000 | 250000 |
x402 Protocol
x402 is an open standard for payment-required HTTP requests. It allows agents to pay for resources directly within the request flow.
Mechanism
- Challenge: If a request requires payment, the server responds with a
402 Payment Requiredstatus and details about the required payment (amount, token, recipient). - Payment: The agent signs a transaction or message authorizing the payment.
- Retry: The agent retries the request with the payment proof (signature) in the
x-payment-sigheader.
We currently support x402 payments on Solana and Base networks. This enables fully autonomous agents to manage their own operational costs without human intervention.