ANONYMOUS

ANONYMOUS // PRIVATE API

agentic endpoint for offensive security · one key, one VM
console

ANONYMOUS is an autonomous operator welded to a Kali VM: it plans, runs the tools, reads the output and reports back. This endpoint gives you that same operator privately — every API key owns one Docker VM of its own, with its own disk, its own scope list and its own conversation. Calls carrying your key are routed to your VM and to nothing else.

Private by construction. Your container publishes no ports at all; the only way in is a docker exec from the host that created it. Nothing you do is visible to another key, and the engagement stays between you and your own VM.
18+ · your responsibility. This API drives offensive tooling. You must be 18 or older to use it, and you may only point it at systems you own or have written permission to test. Signing the rules of engagement records who authorised what, for which hosts and until when — it is the licence, and the scope list is the limit. You alone are accountable for what the operator does with your key, your authorisation and your targets. See 6 · Age, responsibility and lawful use.

1 · Get a key

TOR Anonymous Wallet — the subscription and the key live on one wallet.

Register a username and a password (or sign one in) and the key you mint here is bound to that wallet's TOR address — it inherits the wallet's membership on chain, so revoking the subscription revokes the key with it. Inside the wallet: TOKEN HOLDINGS, NFT HOLDINGS, TRANSACTION HISTORY, SEND / RECEIVE, API KEY MANAGEMENT and BUY TOR, each one a real call to the OneNess TOR node.

not signed in
curl -s -X POST http://127.0.0.1:8420/v1/keys \
  -H 'Content-Type: application/json' \
  -d '{"label":"my engagement"}'
{
  "key": "anon_3fT...<shown once>",
  "key_id": "9c1f4a2b7d10",
  "container": "anon-vm-9c1f4a2b7d10",
  "docs": "/api-docs"
}

The raw key is shown once; only its SHA-256 digest is stored. There is no payment step yet: the key is the only authenticator for now.

Try it here
keys are minted on this machine only

2 · Send the orders

Authentication is the key, in either header:

Authorization: Bearer anon_...
X-API-Key: anon_...

Then talk to your VM. The same orders work over HTTP and inside a chat message:

OrderEndpointWhat happens
AnonymousPOST /v1/vm
or {"message":"Anonymous"}
Docker is started if it is down and your VM is created/started.
Anonymous Set Target <host> POST /v1/targets
{"target":"example.com","mode":"intrusive"}
Writes a new scope into your VM's target list. Prefix it with recon (Anonymous Set Target recon example.com) for read-only work; comma-separate several hosts to add them at once.
Anonymous Delete Target <host> DELETE /v1/targets?target=example.com Takes that scope back out — the host and anything under it. The VM keeps running; ANONYMOUS simply loses the authorisation.
Anonymous Authorize POST /v1/authorize Accepts every scope ANONYMOUS suggested while working and adds them to the list as yours, so it never has to ask again.
Anonymous /byePOST /v1/vm/bye The VM is shut down. Its disk, /work and your key survive.
Anonymous DeleteDELETE /v1/vm The VM and its /work are deleted for good. The key survives and can build a clean VM.
Anonymous StopPOST /v1/stop Everything running is halted (including the command inside the VM) and the VM waits for your next message.
Anonymous set api key <key> {"message":"Anonymous set api key anon_..."} Authenticates and binds the caller to that key's VM. Unknown keys are refused.
Anonymous Help {"message":"Anonymous Help"} The card: every order above with a one-line description. Nothing is started or touched, so it works before Anonymous.

The scope list is yours: ANONYMOUS proposes, you accept. Every host it asks for is queued as a suggestion and shows up in GET /v1/targets with "by":"agent" until you accept it — then it is "by":"operator".

3 · Endpoints

MethodPathAuthReturns
GET/v1/healthnone Docker, image, network, model key state and how many keys exist.
POST/v1/keysnone A new key (shown once) and the container it will own.
GET/v1/mekey Your key, your VM, its IP, turns used, the scope list and every order.
POST/v1/chatkey {"message":"..."} → the operator's final answer, steps, usage and the VM state. Lifecycle words are accepted here too.
POST/v1/vmkey Start Anonymous: Docker + your VM.
GET/v1/targetskey Your scope list: targets (by = agent or operator) and the scopes ANONYMOUS suggested.
POST/v1/targetskey {"target":"...","mode":"recon|intrusive"} → Anonymous Set Target: add a scope.
DELETE/v1/targetskey ?target=... → Anonymous Delete Target: remove a scope and everything under it.
POST/v1/authorizekey Anonymous Authorize: accept every suggested scope.
POST/v1/vm/byekey Shut the VM down, keep the disk.
DELETE/v1/vmkey Delete the VM and its /work.
POST/v1/stopkey Halt everything running, keep the VM.
DELETE/v1/keyskey Destroy the key and its VM.

4 · A whole engagement, curl

KEY=$(curl -s -X POST http://127.0.0.1:8420/v1/keys \
        -H 'Content-Type: application/json' -d '{"label":"lab"}' \
        | python -c "import json,sys;print(json.load(sys.stdin)['key'])")

curl -s -X POST http://127.0.0.1:8420/v1/chat \
  -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' \
  -d '{"message":"Anonymous"}'

curl -s -X POST http://127.0.0.1:8420/v1/chat \
  -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' \
  -d '{"message":"Anonymous Set Target recon scanme.nmap.org"}'

curl -s -X POST http://127.0.0.1:8420/v1/chat \
  -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' \
  -d '{"message":"Recon 10.10.10.5 with nmap, then report the open ports and versions."}'

curl -s -X POST http://127.0.0.1:8420/v1/authorize -H "Authorization: Bearer $KEY"
curl -s "http://127.0.0.1:8420/v1/targets" -H "Authorization: Bearer $KEY"
curl -s -X DELETE "http://127.0.0.1:8420/v1/targets?target=scanme.nmap.org" \
  -H "Authorization: Bearer $KEY"
curl -s -X POST http://127.0.0.1:8420/v1/stop -H "Authorization: Bearer $KEY"
curl -s -X POST http://127.0.0.1:8420/v1/vm/bye -H "Authorization: Bearer $KEY"

/v1/chat answers when the run finishes — a real engagement can take minutes, so set a generous client timeout.

5 · What the operator can do

Everything the console can: recon and enumeration, web exploitation, credential attacks with hydra/sqlmap/nuclei, shells and post-exploitation, loot to /work/loot/, plus the page toolkit (page_open, page_view, page_click, page_type, page_submit, page_extract) for scraping, locators, logins and account_create — which signs up on a platform with a generated identity and hands back the credentials and any developer API key it finds.

6 · Age, responsibility and lawful use

You must be 18 or older to use this API. ANONYMOUS is an offensive security tool: it will run reconnaissance, exploitation and post-exploitation tooling against whatever you authorise, and the swarm will not stall to ask you whether it should.

The same card is in the product: about in the terminal, Anonymous About in the console.

7 · Errors

StatusMeaningFix
401No key, or a key this server never issued. Mint one with POST /v1/keys and send it as a bearer token.
409The console is already running an instruction. Wait for the run to end, or POST /api/cancel.
429The key cap for this host is reached. Delete an unused key with DELETE /v1/keys.
200 + "ok": falseThe run failed (VM down, model error, bad order).Read message; the VM state is in vm. Fix and resend.