Build with an AI agent
poe-buildwright is an unofficial, fan-made Path of Exile 2 build planner designed to be driven by AI agents as first-class users: an agent can create, validate, and share a complete build — passive tree targets, leveling snapshots with respecs, skills with supports, grounded gear, and annotated picks — without a login, an API key, or a browser.
The whole loop, for humans in a hurry
Paste this to any assistant that can browse:
Read https://<this-site>/llms.txt and make me a Warrior earthquake build with leveling snapshots. Give me the share link.
The agent reads the contract, grounds every name in the game's own data, and hands back a link. What you open is yours to edit — nothing is stored server-side.
The machine surface
| Resource | What it is |
|---|---|
| /llms.txt | The authoring contract: plan format, grounding rules, snapshots/respecs, the finish line |
| capabilities.json | Endpoint discovery — what this deployment supports, patch, schema version, slot aliases |
| openapi.json | OpenAPI 3.1 spec for the endpoints below |
| schema.json | JSON Schema for the poe2-agent-plan format |
| primer.md | PoE2 fundamentals for agents: budgets, defence layers, archetypes, known mistakes |
| examples/index.json | Known-good plans, toy to full-size (one authored end-to-end by an agent, 99/99 points) |
POST /agent/build | The one-shot finish: plan in → validated share_url + agent_url + points + note accounting out |
POST /agent/validate | The same validation report without minting URLs — for repair loops (coded diagnostics, per-target costs, budget hints) |
PUT /live/<token> | Live collaboration: a human watches the agent's revisions appear on their tree in real time |
Grounding data
Agents never guess names. The site serves the game's own data as JSON: passive notables with per-class path costs, the full connectivity graph, every skill gem with type algebra (plus precomputed support compatibility), equipment bases and the real affix vocabulary — all mined first-party from the game's CDN, refreshed per patch.
Why it works
- Targets, not travel nodes — agents name the notables they want; a deterministic pathfinder does the graph search.
- Validation before delivery — point budgets, reachability, gem/support compatibility, gear grounding, leveling realism; failures come back as machine-branchable diagnostics with repair hints.
- Annotations survive — build notes, snapshot notes, and per-pick notes flow into the planner's guide timeline and the share link.
- Nothing stored — share links carry the whole build in the URL; what a user opens lives in their browser.