Agent integration

Computalot is built for autonomous agents. The fastest start is to install the skill.

Step 1: Install the skill

Paste this into your agent:

Fetch https://computalot.com/skill.md and follow it to set up Computalot
(on-demand GPU/CPU compute). Then use it to <describe your workload>
and report the results.

The skill teaches your agent to authenticate, create projects, submit jobs, and get results.

Step 2: Get access

Your agent needs one of:

• An API key (flk_...)
• A wallet session (fls_...) from the challenge → sign → verify flow

Open access. Your agent can self-onboard with any wallet (challenge → sign → verify). Then it tops up over x402 or MPP. Computalot issues API keys on request through the waitlist at https://computalot.com/.

Step 3: Submit feedback

We want feedback from your agent. When your agent finds a problem or a possible improvement, it must submit feedback automatically:

curl -sS -X POST https://computalot.com/api/v1/feedback \
  -H "Content-Type: application/json" \
  -d '{"type": "bug", "title": "Brief summary", "description": "Details..."}'

The types are bug, feature_request, provisioning, and job_type_request. No auth is required.

Alternative: read the API reference directly

For agents that consume raw API documentation:

curl -sS https://computalot.com/llms.txt

A more detailed version with tutorials is at /llms-full.txt.

How agents authenticate

API key — set flk_... as the bearer token. Computalot issues keys on request through the waitlist.

Wallet auth + funding:

1. POST /api/v1/auth/wallet/challenge — request a challenge
2. Sign the challenge with the agent’s wallet
3. POST /api/v1/auth/wallet/verify — exchange the signature for a session token (fls_...)
4. GET /api/v1/account/balance — read credits
5. If the account needs credits, pay the top-up quote over x402 (PAYMENT-SIGNATURE) or MPP (Authorization: Payment). See Billing

What agents can do

Projects (your code):

1. POST /api/v1/projects — create a project
2. POST /api/v1/projects/:name/push — upload code
3. POST /api/v1/jobs — submit a job immediately after push
4. Optional: POST /api/v1/projects/:name/init — prepare currently available workers before a burst
5. GET /api/v1/results/:job_id — get results

Documentation URLs