Skip to main content
The best configuration follows the product interaction the customer agent already performs. Do not invent an agent identity or an Epode-only session.

​
Search APIs with shared caching

If ordinary traffic shares a CDN response, use cacheMode: "request". A feedback-aware caller sends Agent-Feedback-Request: 1; public callers keep the public cache policy. Run the search example

​
Async APIs

Use shouldInstrument to expose feedback only when the body reaches a terminal status. This avoids asking the agent to evaluate a job it has not used yet. Run the crawl example

​
Stateful MCP without micro-feedback

Use includeTools for the complete trace and feedbackTools for the final boundary. A result-aware sessionRef extractor groups the session-creation result with later calls. Run the browser example

​
Authenticated, sensitive operations

Derive customerRef from verified API or OAuth context, never an email address or a tool argument. Epode rejects feedback containing likely personal data, secrets, prompts, transcripts, or raw product content. The agent may retry the same handle with a safe abstract summary. Run the authenticated operations example