Agent First Interface

Scaffold tools your agents read first.

One manifest. Three surfaces — CLI, MCP, HTTP — each shaped by a different agent-ergonomic discipline. One command: afi.

What is AgentCulture? The paradigm

Quickstart

uv tool install afi-cli
afi explain afi              # top-level map
afi overview                 # cross-surface rollup
afi learn                    # structured self-teaching prompt for an agent

uv tool install is the supported install path — not pip install.

The three surfaces

CLI — learnability

A learn affordance so an agent can introspect the tool and author its own usage skill in one shot.

MCP — minimalism

A deliberately small menu. Every verb is a decision point; fewer verbs, better calls.

HTTP — discoverability

Markdown pages plus a sitemap. Any agent with a fetch tool can navigate.

This site ships a sitemap.xml — that's the HTTP principle applied to afi-cli itself.

Read next

AgentCulture

The OSS org, its agents-as-members model, and where afi-cli sits inside it.

Agent First

The paradigm — the human-vs-agent design reversal and the three interface disciplines that follow from it.

The Rubric

The mechanical bundles afi cli verify runs against any CLI. afi-cli itself has to pass.

Links

• Repo: https://github.com/agentculture/afi-cli
• PyPI: https://pypi.org/project/afi-cli/
• Sibling: agex-cli — agent experience inside a repo (hooks, CI, workflow). afi-cli is the agent’s interface to a tool.