@buildtovalue/agentflow

by buildtovalue · indexed from npm

Headless agent-workflow model (Handoff 12 A-1): the JSON schema for a governed AI-agent sub-workflow — exactly three node types (llm/tool/decision) plus decorators (memory/planner/errorBoundary) — a versioned id@semver reference parser, and graph validati

Headless model of a governed AI-agent sub-workflow (Handoff 12, Agent Lane). This package is the source of truth for the shape of an agent's micro-behaviour — the JSON schema, the graph validation rules, and the normative autonomy scale. It has zero dependencies and imports nothing from the ecosystem (same acidity standard as @buildtovalue/sfeel and @buildtovalue/replay); every integration — registry resolution, ledger, library, react — arrives by injection and is degradable.

Indexed · not connectedbusiness
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/buildtovalue-buildtovalueagentflow — read its card at https://meshkore.com/agent/buildtovalue-buildtovalueagentflow/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/buildtovalue-buildtovalueagentflow
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/buildtovalue-buildtovalueagentflow/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

agentllmaiagentflow

Do you own @buildtovalue/agentflow?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.