A test bench for AI agent tools

MockAgentTest the tool calls your agent hasn't made yet.

Build realistic mock endpoints for the tools your AI agent depends on. Validate inputs, exercise edge cases, and replay calls before connecting to production services.

Start building Log in to your workspace

JSON Schema validation No live service calls Inspect every run

workspace / tools / issue_refund

GATEWAY ONLINE

Execution log

Recent tool calls

LIVE

issue_refund

{ "user_id": "vip" }

SUCCESS

42 ms

issue_refund

{ "reason": "missing id" }

SCHEMA ERROR

58 ms

Every request leaves a trace you can inspect and replay.

Scenario response

VIP user

MATCHED

POST /api/v1/mock/tool_id

input
{
  "user_id": "vip",
  "reason": "duplicate"
}

mock response
{ "success": true,
  "message": "VIP refund processed." }

Add bearer-key protection when a mock is ready to share.

Explore the workflow

Why MockAgent

Build the integration before the real integration is ready.

Agent tool calls are hard to test when the service is unfinished, expensive, rate-limited, or capable of real side effects. MockAgent gives each tool a predictable HTTPS endpoint, so you can iterate on schemas and agent behavior in a controlled workspace.

Make the contract explicit

Define the arguments your tool accepts with JSON Schema. Invalid calls come back with specific errors your agent can correct.

SCHEMA VALIDATION

Exercise more than the happy path

Match inputs to named scenarios and return different responses. Try edge cases without wiring up real services or test accounts.

CONDITIONAL RESPONSES

Replay and compare

Replay a saved successful call against the current mock. See whether a prompt, schema, or response change altered the result.

REGRESSION CHECKS

Protect the endpoint

Issue revocable bearer keys, require them per tool, and enforce monthly usage limits at the gateway.

API KEY CONTROLS

A simple loop

From tool definition to repeatable test.

Keep the mock endpoint alongside your agent while the real service evolves. Swap the mock for the production tool when you are ready.

Create your first workspace

Describe the tool

Add a name, argument schema, default response, and any conditional scenarios.

Point your agent at it

Use the generated HTTPS endpoint as the tool handler in your agent or test harness.

Inspect and iterate

Review calls, validation failures, latency, and replay comparisons in one workspace.

Start with one tool

Make the next agent run observable.

Create a workspace, define a mock contract, and see exactly what your agent sends back.