Launching today
Manifest
Turn any webpage into an action manifest for AI agents
150 followers
Turn any webpage into an action manifest for AI agents
150 followers
Manifest turns any webpage into a structured JSON map of what an AI agent can click, fill, and submit. One API call, no fragile selectors. Every action comes with resolved CSS/role locators, plus a requires field that encodes dependencies between elements (e.g. "select a plan before this button is clickable"). That's context aria snapshots don't give you. Python SDK, LangChain support, and an MCP server included. Built for anyone shipping browser agents.
the requires field is such a smart touch, encoding dependencies directly into the map saves so much back-and-forth between agent and page. clean SDK and MCP server setup too.
Manifest
@ferhattkge
Thanks, Ferhat — that back-and-forth is exactly what I wanted to cut out. Without the dependency info baked in, the agent's stuck poking at the page to figure out what's actually available, which burns cycles it shouldn't need to. Glad the SDK and MCP setup are landing clean too — appreciate you calling that out specifically.
the requires field for element dependencies is genuinely useful, something I've hacked together badly on past projects. excited to try it with an MCP server setup
Manifest
@hanmtanrkanwyt
Thanks, Hanım — "hacked together badly" is a pretty universal experience with this problem, which is exactly why I wanted it baked into the response instead of something everyone has to rebuild themselves. Hope the MCP server setup makes it an easy first try — let me know how it goes.
@max_nordstrom that's a genuinely honest answer, most tools would just quietly claim it handles all cases. the disabled/aria-disabled inference makes sense as the pragmatic v1 scope. for the async-JS-validation gap, would something like a lightweight 'confidence' flag on the requires field be feasible - even a rough signal telling the agent 'this dependency was inferred from static DOM, verify before relying on it' vs 'this one's a hard disabled attribute' - or would that just push the complexity onto the caller without really helping?
Action manifests are a useful primitive for agent workflows. The part I would want to see emphasized is preconditions and permissions: what the page action is allowed to do, what success means, and what evidence gets handed back after the run.
Manifest
The dependency graph between elements is genuinely useful for agent builders, something I've been piecing together by hand for months. One thing that would save a ton of debugging time: let me simulate an action through the same API and tell me whether the requires chain actually cleared or if something is silently blocking it. Right now I can see the map, but I can't trust it until I try it.
Manifest
The requires field for encoding element dependencies is genuinely clever. It's the kind of context that usually takes teams weeks of brittle DOM mapping to figure out, baked right into the response.
Manifest
@uurk6oe
Thanks, Uğur — that's exactly the gap I was aiming at. Teams end up hand-mapping that dependency logic per site, and it's brittle the moment the DOM shifts, so baking it into the response instead of leaving it as tribal knowledge in someone's scraper script was the whole point. Appreciate you naming why it matters, not just that it exists.
finally something that gets at the real pain point. the requires field encoding dependencies is genuinely clever, going to wire this into our langchain setup this week and see if it holds up on a few gnarly sites.
Manifest
@minekld0
Thanks, Mine — glad it's landing on the actual pain point rather than the surface-level stuff. The LangChain integration should make wiring it in pretty straightforward, but I'd genuinely like to hear how it holds up on the gnarly sites — that's exactly the kind of real-world stress test that surfaces where requires breaks down. Let me know how it goes.