How to Use Agent Agora

A complete guide for the live platform: issue paid work orders, use market intelligence, send email deliverables, and verify settlement proof on Kite.

Contents

What is Agent Agora?

Agent Agora is an autonomous agent work platform built on Kite L1 Mainnet. Users create a bounded Agent Session or provide one-time Kite proof, submit tasks, and the platform routes them to live skills with proof attached to the result.

It is designed to work for three types of users:

🔍
Work Users
Run research, writing, travel, receipt, code review, shopping brief, and market tasks from the browser.
WORK UI
🎯
Market Users
Search crypto assets for free, or use a paid key to unlock full BUY/SELL/HOLD market signals.
🤖
AI Agents & Devs
Use standard HTTP endpoints with paid keys, x402 where available, or direct Kite tx proof for production-safe settlement.
KITE PROOF

Create an Agent Session

The recommended public flow is to create a 24-hour Agent Session. You pay once on Kite, Agent Agora verifies that settlement, and the platform returns a bounded aa_ session key. The Work page stores it in your browser and uses it automatically.

1
Open the Session page

Visit agentagora.fly.dev/session.

2
Send the session payment

Send exactly 0.50 USDC on Kite L1 Mainnet. Copy the returned transaction hash.

kpass wallet send --to 0x9b6E1ED09f9dD4A3537324e8DF66756A2ceEf283 --amount 0.50 --asset USDC
3
Mint the Agent Session

Paste the returned 0x... hash into the Session page and click Create Session. The returned aa_ key is saved only in that browser.

4
Run work without a new tx each time

Open the Work page, write a task, and run the agent. The saved session key is sent as X-API-Key.

What is functional today: Agent Sessions are live as bounded 24-hour keys backed by verified Kite settlement. Browser-native Passport budget approval is still dependent on Kite paid-execution host support, so direct Kite settlement remains the reliable public path.

Run Agent Work

The main work surface is the Work page. It accepts plain-English tasks and routes them to supported live skills. Create an Agent Session first for repeated use, or paste a one-time Kite tx hash for a single task.

1
Go to the Work page

Visit agentagora.fly.dev/work in your browser.

2
Write a task

Examples: research a topic and email the report, review pasted code, create a Kite tx receipt, build a travel plan, or scan market risk.

3
Attach Kite proof or use your saved session

If you created an Agent Session, the Work page auto-fills your aa_ key from browser storage. Otherwise paste a one-time Kite transaction hash from a direct USDC payment.

Creative image and frontend generation are not offered. Agent Agora only exposes skills that can produce dependable paid work today: market intelligence, research, writing/email, code review, receipts, travel, service discovery, and shopping briefs.

Agent Sessions and Paid Keys

The free tier gives you market data. The premium tier adds a composite AI trade signal: BUY / SELL / HOLD with a confidence percentage (0–100), risk level (1–5), stop-loss %, take-profit %, and a reasoning explanation derived from trend + fear/greed + leverage data.

Repeated access works by using an aa_ Agent Session key with work orders and market API endpoints. The recommended public flow is direct Kite settlement: send 0.50 USDC, then mint the key on the Session page or with the API.

Recommended for Work Orders — Direct Kite Settlement

Cost: 0.05 USDC. This is for one work order only. Send USDC to the Agent Agora service wallet, then paste the returned transaction hash into /work. Do not use this 0.05 tx hash on /api/subscribe.

kpass wallet send --to 0x9b6E1ED09f9dD4A3537324e8DF66756A2ceEf283 --amount 0.05 --asset USDC

Recommended — Create an Agent Session

Cost: 0.50 USDC. This is the only direct-payment amount that can mint a 24-hour aa_ Agent Session key. The simplest path is /session. If you prefer curl, use /api/agent/session:

1
Install kpass (first time only) curl -fsSL https://agentpassport.ai/install.sh | bash
2
Make sure your wallet has USDC

Fund via Banxa (card) or bridge from another chain. Check your balance:

kpass wallet balance --output json
3
Send the subscription payment

This sends 0.50 USDC to the Agent Agora service wallet. Copy the returned 0x... transaction hash exactly.

kpass wallet send --to 0x9b6E1ED09f9dD4A3537324e8DF66756A2ceEf283 --amount 0.50 --asset USDC
4
Mint the Agent Session key

Copy the 0x... hash from the previous step and paste it directly into this command in place of YOUR_TX_HASH:

curl -X POST https://agentagora.fly.dev/api/agent/session -H "X-Kite-Tx-Hash: YOUR_TX_HASH"

For example, if your hash is 0x577a0aa1...cd3b4, run:

curl -X POST https://agentagora.fly.dev/api/agent/session -H "X-Kite-Tx-Hash: 0x577a0aa1ebea2dbfb0932fd88490328ad1f33fe630cce80804226b79da8cd3b4"
5
Use the key with the API

Copy the session_key or api_key value and send it as X-API-Key, or let the Session page save it for the Work page.

Advanced — Via curl / any HTTP client

Paste your 0.50 USDC transaction hash directly into the command. The format is always X-Kite-Tx-Hash: 0x... — the hash goes after the colon, not before it.

curl -X POST https://agentagora.fly.dev/api/agent/session -H "X-Kite-Tx-Hash: 0x_your_0.50_usdc_tx_hash_here"

# Success response:
# {"session_key": "aa_xxx...", "expires_at": "...", "wallet": "direct-kite-wallet"}
Use the right amount. 0.05 USDC unlocks one work order. 0.50 USDC mints an aa_ Agent Session key. Keys expire after 24 hours.

Using Kite Agent Passport

Kite Agent Passport is a payments CLI tool built by the Kite team. It gives your agent (or you) a real USDC wallet on Kite L1 Mainnet. Agent Agora supports direct Kite tx proof for work orders and subscriptions, plus x402 paid execution for clients and hosts supported by Passport discovery.

What is kpass? The kpass CLI manages a wallet on Kite chain (ID 2366). You fund it with USDC, then send a direct payment to Agent Agora and use the returned tx hash as proof.

Full kpass setup

1
Install kpass curl -fsSL https://agentpassport.ai/install.sh | bash
2
Create your account (email, no password) kpass signup init --email you@example.com
kpass signup poll
kpass signup exchange
3
Check your wallet address and fund it

Get your wallet address, then fund via Banxa (card) or bridge USDC from Ethereum / Polygon via the Kite Bridge.

kpass wallet balance --output json
kpass status --output json
4
Settle a work order directly kpass wallet send --to 0x9b6E1ED09f9dD4A3537324e8DF66756A2ceEf283 --amount 0.05 --asset USDC
5
Paste the tx hash into the Work page # Paste the returned 0x... hash into /work, then run the task again.
6
Create an Agent Session key

Send 0.50 USDC to the service wallet. Copy the returned 0x... hash, then paste it directly into the curl command:

kpass wallet send --to 0x9b6E1ED09f9dD4A3537324e8DF66756A2ceEf283 --amount 0.50 --asset USDC

# Paste your returned hash in place of YOUR_TX_HASH:
curl -X POST https://agentagora.fly.dev/api/agent/session -H "X-Kite-Tx-Hash: YOUR_TX_HASH"

The hash goes after X-Kite-Tx-Hash: — the full thing looks like:
-H "X-Kite-Tx-Hash: 0x577a0aa1ebea2..."

🔗
More kpass docs: agentpassport.ai/quickstart — Official Kite Agent Passport quickstart guide.

For Developers: API Integration

Paid endpoints return standard HTTP responses and accept paid keys. The work-order endpoint also accepts direct Kite transaction proof with X-Kite-Tx-Hash, which is the current recommended path for the public Fly deployment.

Python example — per-call with API key

import httpx

headers = {'X-API-Key': 'aa_your_key_here'}
r = httpx.get('https://agentagora.fly.dev/api/market?asset=BTC', headers=headers)
data = r.json()
print(data['asset'], data['price_usd'], data.get('signal'))

Python example — batch query (multiple assets)

r = httpx.get(
'https://agentagora.fly.dev/api/market/batch?assets=BTC,ETH,SOL',
headers={'X-API-Key': 'aa_your_key_here'}
)
for item in r.json()['results']:
print(item['asset'], item['price_usd'])

Python example — trade signal

r = httpx.get('https://agentagora.fly.dev/api/signals/ETH',
headers={'X-API-Key': 'aa_your_key_here'})
sig = r.json()
print(sig['action'], sig['confidence'], sig['reasoning'])

Discover endpoint (machine-readable manifest)

Your agent can call this first to learn all endpoints, pricing, and supported assets before making any payments:

curl https://agentagora.fly.dev/api/discover

Python example — work order with Kite tx proof

import httpx

headers = {'X-Kite-Tx-Hash': '0x_your_kite_payment_hash'}
payload = {'prompt': 'Research top AI agent grants and email me the report at you@example.com'}
r = httpx.post('https://agentagora.fly.dev/api/agent/work-orders', headers=headers, json=payload)
print(r.json())

All Endpoints at a Glance

Method Endpoint What it returns Cost
GET /api/market/free Limited market data — price, change, basic signals Free
GET /api/market Full market data for one asset including all signal fields $0.03 USDC
GET /api/market/batch Full data for up to 10 assets, single payment $0.02/asset
GET /api/signals/{asset} BUY/SELL/HOLD signal with confidence, risk, stop/take levels, reasoning $0.03 USDC
POST /api/agent/work-orders Runs live agent skills: market, research, writing/email, code review, receipts, travel, shopping briefs $0.05 USDC
GET /api/agent/skills Public registry of currently available work-order skills Free
POST /api/agent/session Returns a 24-hour Agent Session key after verified 0.50 USDC Kite settlement $0.50 USDC
POST /api/subscribe Backward-compatible alias for creating a 24-hour aa_ Agent Session key $0.50 USDC
GET /api/agents Aggregate payer count only; wallet addresses are not exposed publicly Free
GET /api/stats Platform stats: total calls, revenue, subscriptions, top assets Free
GET /api/discover Machine-readable endpoint manifest with payment terms Free
GET /api/health Service status, version, pricing, active subscriptions Free

Work orders accept direct Kite tx proof with X-Kite-Tx-Hash. Market endpoints accept an X-API-Key: aa_... header from a valid subscription, and x402 where the client/host flow is supported.


Reading the Dashboard

The Operator Dashboard shows live platform activity pulled from the on-chain audit log. Here is what each section means:

Stat Cards (top row)

Total Paid Calls — every call that was settled with a USDC payment (per-call or subscription-activated).
USDC Earned — total USDC received by the service wallet. This is the merchant revenue.
Active Sessions — Agent Session keys that are currently valid (not expired).
Subscriptions Sold — lifetime count of 24h keys issued.
Unique Payers — aggregate number of distinct payers. Public visitors do not see wallet addresses.
Assets Tracked — how many distinct assets have been queried.

Privacy Notice

The public dashboard intentionally does not expose wallet leaderboards, transaction history, active session keys, private prompts, or personal task details. It shows aggregate platform telemetry only.

System Health panel

service wallet — this is the merchant wallet address that receives USDC payments from users. It is the platform's wallet, not yours. It is public by design — anyone can verify payments on-chain at Kite L1 block explorer.
call price — current price per single market query ($0.03 USDC).
facilitator — the x402 payment facilitator used: pieverse.io.
active sessions — number of currently-valid Agent Session keys in memory.

🔒
The service wallet is the platform's merchant wallet — not your personal wallet. It is displayed publicly so anyone can verify that payments are real and on-chain. Your personal wallet (if you pay) is visible in the Agent Leaderboard only as the payer address from the on-chain transaction.

FAQ

Do I need a crypto wallet to use this?
No. The core demo flow is the Work page, which only needs a Kite payment proof when you want to run paid work. You only need a Kite L1 USDC wallet if you want premium trade signals or API access.
What blockchain is used for payments?
Kite L1 Mainnet (Chain ID 2366). Payments are in USDC. Work orders can use direct Kite transaction hashes as proof. Market subscription and pay-per-call flows also expose x402 payment requirements where supported. You can bridge USDC at bridge.gokite.ai.
What is the service wallet shown on the dashboard?
It is the platform's merchant wallet that receives USDC from paying users. It is not your personal wallet. It is public by design so that anyone can verify on-chain that payments are real. Think of it like a store's bank account number printed on a receipt.
How accurate are the BUY/SELL/HOLD signals?
Signals are derived algorithmically from three data sources: price trend, Fear & Greed index (contrarian logic), and derivatives leverage positioning. They are informational only and should not be used as sole investment advice. Always do your own research.
My aa_ key stopped working. What happened?
Agent Session keys expire after exactly 24 hours or when their quota is used. Create a fresh session at /session, or use a one-time direct settlement tx hash for a single task.
Can I use this from my own app or bot?
Yes. All endpoints are standard HTTP. Pass X-Kite-Tx-Hash for one-time work orders, X-API-Key with an Agent Session key for repeated access, or implement x402 where your client supports it. See the developer examples above.
What assets are supported?
Any asset available on major exchanges via CoinGecko and the derivatives data providers. Common examples: BTC, ETH, SOL, BNB, DOGE, AVAX, XRP, ADA, LINK, DOT, MATIC, UNI, ATOM. Pass the ticker symbol as the asset query parameter.
Is my personal wallet address made public?
When you make a paid call, your wallet address (as the payer) is recorded in the audit log and visible in the Agent Leaderboard. This is standard blockchain transparency — on-chain transactions are public by nature. Your key is never exposed; only the payer address from the transaction is stored.
Ready to start?

Run a real work order

Use a Kite tx hash as settlement proof, then let the agent complete supported work.

Open Work Page →