What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: send and chase invoices.Similar tools
Listed for the same task: send and chase invoicesReviews
No review yet. Used Autonomous Agents Network (AANet)? Be the first to help others choose.What it does
Autonomous Agents Network (AANet) is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: invoicing. That makes it a candidate for tasks such as send and chase invoices.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2h ago (live check)Hosted endpoint
https://aanet.space/mcpstreamable-http
In Claude Code: claude mcp add --transport http aanet https://aanet.space/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"aanet": {
"url": "https://aanet.space/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 2h agoONLINE Autonomous Agents Network (AANet) answered an MCP connection on 17 Nov 2026 and introduced itself as aanet (MCP protocol 2025-06-18).
35 tools offered to AI assistants
aanet_create_workspace· Create a real AANet workspace with a prepaid USDC balance — the entry point for an orchestrator agent starting a new swarm task. Use aanet_create_trial_workspace instead if you want to explore the API before paying anything. On success, retaanet_create_trial_workspace· Create a free trial workspace — no payment, no arguments, works immediately. Use this instead of aanet_create_workspace when you want to exercise the API (files, locks, sub-keys, messages) before committing real money. Pre-funded with a smaaanet_get_remaining_balance· Free (never charged): how much this key can still spend, so you can stop before a 402 instead of discovering it mid-sequence — the MCP counterpart of the REST X-AANet-Remaining-Balance header. Takes only the key; works for the owner_key oraanet_get_workspace· Check a workspace's current balance and status — the read-only counterpart to every other workspace tool. Works with the owner_key or any sub-key issued under it (not restricted to the owner). Returns deposit_balance and total_spent in rawaanet_delete_workspace· Permanently and irreversibly delete a workspace: every sub-key, all files, the activity log, and any registered webhooks are destroyed along with it — there is no undo and no trash/recycle bin. Requires the owner_key; a sub-key gets a 403.aanet_deposit· Fund a real workspace via the x402 protocol — a two-step call using the same tool both times. This does not accept trial workspaces (use aanet_create_workspace for a fundable one) and requires the owner_key. Step 1 — call with only api_key/aanet_mint_subkey· Issue a new scoped credential for one sub-agent — the standard way to bring a sub-agent into an existing workspace. Requires the owner_key; a sub-key cannot mint another sub-key. Returns {subkey_id, key} where key is shown exactly once, theaanet_list_subkeys· List every sub-key ever issued under a workspace (including revoked ones), with each one's scope, budget_cap, window/rate limits, and spent_so_far — the inventory view that complements aanet_get_activity's per-event log. Owner_key required;aanet_update_subkey· Change a live sub-key's scope and/or budget cap without revoking and reissuing it — use this instead of aanet_revoke_subkey + aanet_mint_subkey when the sub-agent's credentials themselves should keep working (e.g. widening its file scope miaanet_revoke_subkey· Permanently revoke one sub-agent's credentials — every subsequent call with that key gets a 401. Use this when a sub-agent is compromised, misbehaving, or simply finished, without affecting any other sub-key in the workspace. Owner_key requaanet_read_file· Read a file's content, or list a directory's entries if path points to one — the read counterpart to aanet_write_file/aanet_append_file. Costs 1 unit per hit (file or directory); a missing path returns 404 and is free. Returns {path, contenaanet_write_file· Overwrite a file's entire content, creating it if it doesn't exist — use aanet_append_file instead if you want to add one entry without replacing what's there. Fires a file_write webhook event on success (see aanet_register_webhook). Pass i
Show 23 more
aanet_append_file· Append one entry to a file without touching what's already there, creating the file if it doesn't exist yet — use aanet_write_file instead when you need to replace the whole file. Typical use: a shared log or running notes file multiple subaanet_delete_file· Permanently remove a file — the missing piece of the file lifecycle alongside aanet_read_file/aanet_write_file/aanet_append_file. There is no undo: to recover, a sub-agent would need its own backup of the content. Fires a file_delete webhooaanet_acquire_lock· Claim exclusive ownership of a named unit of work so no other sub-agent starts the same thing — call this before starting work, not after. Returns {lease_expires_at, fence} on success, or a 409 if another sub-agent already holds an unexpireaanet_renew_lock· Extend a lock you currently hold, before its lease runs out — call this instead of aanet_acquire_lock again while work is still in progress. Fails with 404 if nobody holds the lock, or 403 if a different sub-key is the current holder (you caanet_release_lock· Voluntarily give up a lock you hold, immediately, instead of waiting for its lease to expire — always call this as soon as you're done with the unit of work, so a sub-agent waiting on it doesn't idle unnecessarily. Free (no charge), unlikeaanet_get_lock_status· Check a lock WITHOUT trying to take it, and tell "nobody ever took it" apart from "someone took it and released it" — a free lock and an already-finished task look identical from aanet_acquire_lock alone. Returns status held | expired (leasaanet_get_activity· Read the server-side audit log of every attempt in this workspace, successful or rejected — the authoritative source of what each sub-agent actually did, since sub-agents can't fake or skip this the way they could misreport their own actionaanet_get_activity_summary· Spend totals from the audit log instead of reading every entry: for each group, total_cost (units) and calls. Use it to see which sub-agent is burning budget before adjusting a budget_cap via aanet_update_subkey. Owner_key required. An unknaanet_get_activity_head· Signed tip of the workspace's tamper-evident activity chain: every successful (OK) audit row is hash-linked to the previous one, and this returns {seq, entry_hash, signed_at, key_id, algorithm, signature} - an Ed25519 signature by the serviaanet_export_activity· Export the hash-chained (OK) audit rows in ascending order with prev_hash/entry_hash, plus the signed head of the whole chain. Page forward with since_seq = the last chain_seq you got. Verify it yourself with the ~25-line verify_chain functaanet_get_forecast· Burn rate and runway: the workspace balance, spend per hour over the last 1h / 24h / 7d (each window shortened to the workspace's age if it is younger) with the hours the balance would last at that pace, and the top spending sub-keys of theaanet_submit_feedback· Report a bug, request a feature, or flag that pricing feels wrong — this is the one feedback channel into how the operator prioritizes what to build next, not a support ticket that gets a reply. Any valid, unrevoked key can call this, owneraanet_submit_signal· If you looked at this server and decided NOT to use it — this tool is for you. No api_key needed (you never created a workspace, so you have no key); nothing is billed. One honest call tells the operator what stopped you, which is the one saanet_request_refund· Ask for a workspace's entire remaining balance back, when its task is done and money is left over — call this before aanet_delete_workspace, not after. Owner_key required; trial workspaces reject this outright (they never held real money).aanet_get_refund_status· Check the status of every refund request ever made for a workspace — the way to find out whether an aanet_request_refund call actually got paid. Owner_key required. Each entry has status ("pending", "paid", or "rejected"), and tx_hash onceaanet_send_message· Send a one-shot signal directly to another sub-agent (or to everyone), for things that don't belong in a file — e.g. "chunk 3 done" or "aborting, don't wait on me". Use aanet_write_file / aanet_append_file instead for anything that needs toaanet_get_messages· Fetch messages sent via aanet_send_message — the pull-based fallback for when you haven't registered a webhook on the message event. With `wait` > 0 the call parks until a matching message arrives (or the timeout), so an agent that cannot raanet_register_webhook· Register a push endpoint so this workspace calls you instead of you calling aanet_get_activity/aanet_get_messages/aanet_acquire_lock in a polling loop — the main alternative to polling anywhere in this API. Owner_key required; up to 5 activaanet_list_webhooks· List webhooks registered on a workspace — url, subscribed events, consecutive_failures (failed attempts since the last success), and disabled_at/disabled_reason if it was auto-disabled after 10 failed attempts in a row (you also get an aaneaanet_delete_webhook· Permanently remove a registered webhook — no further events will be delivered to it, active or auto-disabled. Owner_key required. There is no way to temporarily pause one; delete and re-register with aanet_register_webhook if you want it baaanet_get_pricing· Free, no key needed: the machine-readable price list — cost in units ($0.00001 each) of every operation (base + per started KB where it applies, and when it is free), the minimum deposit, file-size and webhook limits, trial terms and the idaanet_estimate_savings· Estimate the cost of coordinating a swarm on AANet versus relaying the same coordination through your orchestrator's LLM context — before you create a workspace or spend anything. Same formula as the calculator at https://aanet.space/#savinaanet_get_webhook_deliveries· Inspect one webhook's delivery history — use this to debug a webhook that seems to have gone quiet (check aanet_list_webhooks first to see if it's been auto-disabled) or to confirm an event actually fired. Owner_key required. Each entry has
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.8.0 | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Hosted endpoint | https://aanet.space/mcp | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Website | https://aanet.space | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 19h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 19h ago |
Change history
- VERSION21 Oct 20261.6.0 → 1.8.0
- VERSION21 Oct 20261.5.0 → 1.6.0
- VERSION21 Oct 20261.4.0 → 1.5.0
- VERSION21 Oct 20261.3.0 → 1.4.0
- VERSION09 Oct 20261.2.1 → 1.3.0
- VERSION08 Oct 20261.2.0 → 1.2.1
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Autonomous Agents Network (AANet) still online?
Free alerts · no account▲ 0Do you run Autonomous Agents Network (AANet)? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Autonomous Agents Network (AANet)
How do I connect Autonomous Agents Network (AANet)?
Use the hosted endpoint https://aanet.space/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Autonomous Agents Network (AANet) offer?
When Electra Index connected on 17 Nov 2026, it listed 35 tools: aanet_create_workspace, aanet_create_trial_workspace, aanet_get_remaining_balance, aanet_get_workspace, aanet_delete_workspace, aanet_deposit, aanet_mint_subkey, aanet_list_subkeys and more. The full list is in "Live check" above.
Is Autonomous Agents Network (AANet) online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2h ago.
What can I use Autonomous Agents Network (AANet) for?
Based on its description, it is most relevant to: send and chase invoices.