Skip to main content
AgentsUse

Coming soonAccounts and the planned features are not open yet.See what is planned

Agent tooling startup

AgentsUse builds the tools AI agents use.

We are building APIs, MCP servers, and SDKs for agent runtimes. The work starts from a simple observation: a model can only act through the tools it is given, and those tools need contracts, permissions, and operating limits that hold up outside a demo.

24 tools · 19 MCP servers · 6 frameworks · 4 stacks · 34 guides · 9 harness patterns

What we build
APIs, MCP servers, and SDKs that give agents a defined way to search, read, compute, and act.
How agents should run them
Through a harness that validates calls, gates consequential actions, budgets results, and records the run.
Why the catalog is public
It maps the tool layer agents use today, with setup, limits, and sources builders can check.

Live today

Live today

Coming soon

Coming soon
For vendors: claim a listing

The Harness

A tool call needs an operating layer.

The harness sits between a model and its tools. It checks arguments before execution, holds consequential calls for approval, sets timeouts and retry bounds, controls how much of a result re-enters context, and leaves a record a reviewer can read. AgentsUse publishes nine patterns for that layer, three long-form guides, and notes inside selected profiles.

The AgentsUse framework is in the works, not shipped. Request early access

Guides

Operating judgment for agent work

Delegation, permissions, failure handling, evaluation, cost, and handoff, written for the person who owns the result.

Guide

10 Tasks AI Agents Handle Well (and 5 to Keep in Your Hands)

Where AI agents earn their keep in 2026 and where they still fall short. A decision grid for delegating checkable, low-cost work and keeping judgment, money, and public commitments in human hands.

2026-09-26

Guide

Comparing AI Agent Frameworks

Framework marketing converges on the same claims. The dimensions that matter for choosing: control, observability, tooling, deployment, cost, and team fit, plus a 30-day evaluation plan and the build-versus-buy math.

2026-09-29

Guide

A Checklist Before Letting an AI Agent Touch Real Work

Twelve checks before an agent touches customers, money, or public communication. Covers least-privilege access, written instructions and limits, trial runs, action logs, and rollback, calibrated by risk tier.

2026-09-26

Guide

Agent Security Risks You Must Handle

Agents read untrusted content, run code, and call APIs with your credentials. The risks that materialize in production, from prompt injection to credential leakage, and the layered mitigations that contain them.

2026-09-29

Guide

How to Choose an AI Agent for a Specific Task

A job-first framework for choosing an agent for one specific task. Write the job down, score candidates on five criteria, run a same-task test on your own inputs, and cost the winner before it touches real work.

2026-10-04

Guide

When Not to Use AI Agents

Knowing when not to deploy an agent is a core operating skill. Where agents are overkill, where they are dangerous, the hidden costs of defaulting to them, and what to use instead.

2026-09-29

AgentsUse is building the tool layer AI agents run on. The catalog stays public because it is the map we build from: what agents can call today, where the contracts are thin, and where a better tool should exist.

Know a tool, server, or framework the map is missing? Suggest it for review. Submissions enter a queue and are never published automatically.