Skip to main content
Epode helps companies see AI traffic and understand what those customers want. The goal is to help companies convert more of that traffic, but the product mechanism for doing so remains an open question. The current product foundation has two parts. AEO observes how a company appears in AI and what traffic reaches it. The agent experience graph is the core product for understanding the customer’s goal, constraints, choices, and path. Captured answers, observed traffic, verified interactions, and business outcomes remain distinct evidence; lower-funnel totals are not AEO attribution until they are linked. The company connects Epode once. Customers do not need to create an Epode account, install a product-specific plugin, or send product keys anywhere.

Measure AI visibility

Build a buyer-journey query portfolio and keep every result tied to its evidence level.

Serve an agent experience

Publish a merchant-authored need graph that agents can safely traverse.

Connect a product

Add one company-side integration and keep every normal product response fail-open.

Understand customer context

See how permission, provenance, expiry, and known or anonymous identity fit together.

​
The product model

Journeys and customers are linked; context a customer agent shares appears on the journey that used it. Setup, memory, connectors, and data controls live under Configurations.

​
The loop

1

Arrive

A customer agent opens the product. Humans and crawlers still receive ordinary HTML; known agent clients can receive a machine-readable guide at the same URL.
2

Ask

On an eligible product response, Epode can request missing customer context or expose the next merchant-authored need edge. The agent answers from the current task, asks the customer, reports no relevant context, or declines.
3

Learn

The agent sends only bounded, task-relevant need state or permissioned context. Epode records the journey hop, permission, provenance, confidence, allowed use, and expiry.
4

Personalize

Ranked results use the expressed need state and any separately permissioned remembered context.
5

Measure

Journey hops, product evaluations, and business outcomes become ordinary Epode session and interaction telemetry.
Epode is identity-aware, never identity-inventing. The company supplies verified accountRef or userRef, a product-owned anonymousRef, or no stable identity at all. Epode never discovers a person’s identity from an IP, fingerprint, prompt, or agent claim.