Custom Mock Agents
Custom Mock Agents are fully configurable A2A-compliant agents you create within Agent Explorer. Unlike the built-in mock, each custom mock agent has its own AgentCard, skills, response logic, and A2A endpoint.
Why Custom Mock Agents?
| Use Case | Description |
|---|---|
| Protocol testing | Test your client against a known-good A2A implementation |
| Skill simulation | Simulate specific agent skills with controlled responses |
| Error scenarios | Test how your client handles errors, delays, and edge cases |
| Team demos | Share a stable mock agent with your team via team ownership |
| CI/CD | Use the mock agent endpoint in automated tests |
Creating a Mock Agent
Navigate to Projects → New Project and choose to create a Mock Agent. This opens an 8-step wizard:
Step 1 — Basic Info
- Name — Display name for the agent (required)
- Description — What this agent does
- Version — AgentCard version string (e.g.,
1.0.0) - Icon URL — Optional icon for the agent
Step 2 — Interfaces
Configure the protocol interface endpoints. For mock agents, this is auto-populated based on the agent's URL. You can customise the protocolBinding (JSONRPC) and protocolVersion.
Step 3 — Capabilities
Toggle capabilities the mock agent will advertise:
| Capability | Description |
|---|---|
| Streaming | Advertise SSE streaming support |
| Push Notifications | Advertise push notification support |
| State Transition History | Include state history in responses |
| Extended AgentCard | Support extended AgentCard format |
Step 4 — Skills
Define one or more skills. Each skill has:
- ID — Unique identifier (used in routing)
- Name — Display name
- Description — What the skill does
- Tags — Searchable tags
- Input/Output Modes — MIME types (defaults to
text/plain)
Step 5 — I/O Modes
Set default input and output MIME types for the entire agent.
Step 6 — Provider
Set the organisation and URL of the provider (metadata only).
Step 7 — Response Behaviour
Configure how the mock agent responds. See Response Behavior for full details.
Step 8 — Review
Preview the full generated AgentCard JSON, review validation status, and save.
Mock Agent Endpoint
After creation, the mock agent is available at:
{base-url}/api/mock-agents/{agent-id}/a2a
The AgentCard is served at:
{base-url}/api/mock-agents/{agent-id}/.well-known/agent-card.json
Editing a Mock Agent
Open the project that uses the mock agent and click Edit Agent. This re-opens the 8-step wizard pre-populated with the current configuration. You can save at any step.
Ownership
Mock agents can be personal (only visible to you) or team-owned (visible to all team members). Change ownership in the wizard's Review step.
API Keys
Mock agents support API key authentication. Generate API keys in Settings → API Keys. Include the key as a Bearer token to restrict access to your mock agent.