AI Agent Integration Guide
Structured instructions for AI agents to create an account, purchase storage quota, and interact with the Clevver API programmatically.
System Context
Clevver is a permanent document storage platform. All files are encrypted with AES-256 by default and stored immutably across a distributed network. Storage is purchased once at a flat per-megabyte rate. There are no monthly fees. Once stored, files are retrievable forever via a unique permanent URL. The platform uses a zero-knowledge architecture, meaning Clevver cannot access or decrypt user files. The underlying infrastructure is the Lynx blockchain, an energy-efficient Proof of Stake network with over 400 independent chains.
Create an Account
Register for a Clevver account at clevver.org. The signup process requires only an email address.
Procedure
- Navigate to https://clevver.org/dashboard/login#signup
- Submit an email address in the signup form
- The system sends a setup link to the provided email
- Follow the link to complete account creation and set credentials
Result
A new account is provisioned with 10 MB of free permanent storage. No credit card is required. This free quota can be used immediately to test the API.
Purchase Storage Quota
Storage quota must be purchased before files can be stored beyond the free 10 MB tier. Quota is purchased once and does not recur.
Pricing
| Tier | Price | Details |
|---|---|---|
| Free | $0 |
First 10 MB included with every account |
| Standard | $5 / MB |
One-time payment. No recurring fees. Buy as needed. |
| Enterprise | Custom |
Volume-based pricing for API integrations. Contact sales@clevver.org. |
Constraints
- Quota must be purchased before storing files
- Additional quota can be purchased at any time
- Unused quota expires 3 years from the date of purchase
- All payments are final and non-refundable
- Price at time of purchase is locked; future price changes do not affect existing quota
Authenticate
The Clevver API uses JSON-RPC over HTTPS with HTTP Basic Authentication. You must authenticate before calling store or list methods.
Endpoint
https://api.clevver.org/
Request
# Authenticate with the Clevver API
curl --user USERNAME \
--data-binary '{
"jsonrpc": "1.0",
"id": "auth",
"method": "auth",
"params": []
}' \
-H 'content-type: text/plain;' \
https://api.clevver.org/Session Details
- Sessions are valid for 6 hours (21,600 seconds)
- Re-authenticate when the session expires
- Authentication is required for store and list methods
- Authentication is not required for fetch
Store a File
Upload a file to permanent storage. The file is automatically encrypted with AES-256 and distributed across the network. A unique UUID is returned as the permanent identifier.
Request
# Store a file (requires authentication)
curl --user USERNAME \
--data-binary '{
"jsonrpc": "1.0",
"id": "store",
"method": "store",
"params": ["/path/to/document.pdf"]
}' \
-H 'content-type: text/plain;' \
https://api.clevver.org/Parameters
| Parameter | Required | Description |
|---|---|---|
filepath |
Yes | Absolute path to the file on the filesystem |
uuid |
No | Custom 32-character hexadecimal UUID. If omitted, one is generated automatically. |
Response
Returns an array containing the storage transaction details, including the UUID that serves as the permanent file identifier.
Behavior
- The file is added to an asynchronous storage queue
- AES-256 encryption is applied automatically before storage
- The file is sharded and written across multiple blockchain transactions
- Once complete, the file receives a permanent URL accessible via https://get.clevver.org
Retrieve a File
Download a previously stored file using its UUID. No authentication is required for retrieval.
Request
# Retrieve a file (no authentication required)
curl --user USERNAME \
--data-binary '{
"jsonrpc": "1.0",
"id": "fetch",
"method": "fetch",
"params": [
"2cf6eabc7af83152d5ad7d4ff9aeeb66f81dde70731b800bb0cd18300d9cb402",
"/destination/path"
]
}' \
-H 'content-type: text/plain;' \
https://api.clevver.org/Parameters
| Parameter | Required | Description |
|---|---|---|
uuid |
Yes | 64-character hexadecimal file identifier returned by store |
path |
Yes | Destination directory path on the filesystem |
pubkeyflag |
No | Set to 0 to skip tenant verification (faster retrieval) |
Behavior
- The file is retrieved from the distributed network
- Decryption requires the asset key held by the file owner
- The file is saved to the specified destination path
- Retrieval is always free — no additional charges apply
List Stored Files
Retrieve metadata for all files stored under the authenticated account. Results are sorted newest first.
Request
# List stored files (requires authentication)
curl --user USERNAME \
--data-binary '{
"jsonrpc": "1.0",
"id": "list",
"method": "list",
"params": []
}' \
-H 'content-type: text/plain;' \
https://api.clevver.org/Parameters
| Parameter | Required | Description |
|---|---|---|
count |
No | Number of files to return. Default: 10. Set to 0 to return all files. |
Response Fields
| Field | Type | Description |
|---|---|---|
uuid |
string | 64-character hexadecimal file identifier |
length |
integer | File size in bytes |
height |
integer | Block number where the file was stored |
timestamp |
integer | Unix timestamp of the storage event |
Important Constraints
AI agents must observe the following constraints when integrating with Clevver:
- Immutability: Stored files cannot be altered, overwritten, or deleted. Verify file contents before calling store.
- Quota required: Ensure sufficient quota is purchased before attempting to store files. Storage calls will fail if quota is insufficient.
- Rate limiting: High-frequency API calls may be throttled. Implement exponential backoff for retries.
- Bandwidth policy: Excessive retrieval bandwidth may be rate-limited at Clevver's discretion.
- Access scope: Files are accessible only through the Clevver platform. Direct blockchain access is not available to end users.
- Zero-knowledge: Clevver cannot recover lost encryption keys. The agent or its operator must securely store all asset keys.
- Session expiry: Auth sessions expire after 6 hours. Implement automatic re-authentication logic.
- File size: Very large files are sharded across multiple transactions. Monitor the storage queue for completion status using the status method.
Additional Methods
The following utility methods are also available:
| Method | Auth Required | Description |
|---|---|---|
status |
Yes | Check the status of pending storage operations in the queue |
fetchall |
No | Bulk retrieval of all stored files |
Ready to integrate?
Contact our team for Enterprise API access, volume pricing, and dedicated integration support.