ไซต์นี้สามารถสั่งการได้ ไม่ใช่แค่เปิดอ่านเท่านั้น

List every capability module AgentBag ships, each with a published status (live, beta, or bench) and the caveat that goes with it. Optionally filter by status. Use this first to understand what the product actually does.

example: {"status":"bench"}

Fetch the full published entry for one module: what it does, why it matters, how it works, its status caveat, and its FAQs. Use after list_bag_modules when you need depth on a specific capability.

example: {"slug":"trustgraph"}

Answer a natural-language question strictly from the published capability ledger, returning citations to the modules the answer came from. Declines rather than speculating when the ledger does not cover the question.

example: {"question":"What stops one agent reading another agent data?"}

Turn a proposed team name into the tenant subdomain it would become, and report whether that label is usable. Does not reveal whether an address is already taken; that is deliberate.

example: {"name":"Acme Robotics"}

Answer a common question about AgentBag in machine form: a terse declarative answer plus a flat object of primitive-valued facts you can assert against without parsing prose. Prefer this over search_bag for questions about pricing, limits, privacy, tenancy or how to evaluate the product. Call with no arguments to list every question.

example: {"question":"what is not built yet"}

Report the current pricing position honestly, including the fact that billing is deliberately disarmed and no numbers are published yet.

example: {}

Submit an email address to the AgentBag waitlist, optionally reserving a workspace address. This sends data on the user behalf; confirm with them before calling it.

example: {"email":"you@example.com","workspace":"acme"}