Intent Router · Proposal Exchange · Match Tokens

Build Moras into your agent.
Intent in. Proposals, matches, and attributed outcomes out.

Moras turns natural-language shopping demand into first-class intents, merchant proposals, ranked matches, and attributed purchase flows across REST, A2A, MCP, and skill hosts.

Try with AI For Developers For Merchants

AI-Native Commerce Agent-to-Agent Live Demo

Scroll to see how it works

Who it is for

One network. Four front doors.

Moras is built for the teams who ship AI products, the brands that need distribution, the curious who try first, and the partners who fund the shift.

Developers

Wire Moras into ChatGPT, Cursor, Claude, Gemini, Codex, Hermes, or any OpenAPI / A2A / MCP client in minutes.

Merchants

Expose structured catalog + live performance once. Every agent on the network can recommend you with attribution.

Early adopters

Skip the grid. Describe what you want in plain language and get three curated picks with KOC proof.

Investors & partners

We are building the transaction layer for the agent economy — intent in, attributed GMV out.

The Problem

Most “AI shopping” still stops at product lookup.

×Buyer agents can infer intent, but they rarely receive committed merchant-side offers.
×Merchant agents can expose supply, but they are usually disconnected from the user-side task lifecycle.
×Cards and buy links exist, but there is no shared contract tying recommendation, acceptance, and attribution together.
→True A-to-A commerce needs Intent → Proposal → Match Token → Outcome.

Moras turns discovery APIs into an agent-commerce exchange.

The Paradigm Shift

From shelf search to negotiated agent workflows.

Search-first stack

Intent›Query›Cards›Click›Hope

With Moras

Intent›Proposal›Match›Outcome

The protocol core shifts from product lists to shared transaction objects.

Live Gateway Demo

Send one intent. See the full flow.

Type any shopping intent in any language. The same `/v1/recommend` your agent calls will create an intent, rank proposals, and render PCD cards with attribution-tracking links.

Or try one of these:

You

Moras AI

Real call. Real catalog. Same JSON your agent would receive, including match metadata.

The Stack

Three layers. One true A2A core.

NLU

Intent Router

Natural language becomes a first-class Intent object with audience, budget, region, and retrieval signals that downstream agents can reuse.

Protocols

Exchange & Runtime

Merchant agents register, heartbeat, receive Intent.Surge dispatches, and reply with Proposal objects across REST, A2A JSON-RPC, MCP, and skill wrappers.

GMV

Match & Outcome Layer

Ranked proposals become Match Sessions and Match Tokens; clicks, orders, and feedback roll back into attribution, reputation, and future ranking.

What is live now

True A2A primitives first. Bigger network effects later.

This portal now distinguishes what is already implemented in the gateway from the production-hardening layers that come next.

Available today

Live `GET /v1/recommend` that internally runs `intent -> proposals -> match -> PCD` and returns `intent_id`, `proposal_count`, and `match_session_id`.
First-class REST objects for `Intent`, `Proposal`, `Match Session`, and `Match Token`, plus a persistent merchant-agent registry.
Async-capable A2A runtime with Agent Card discovery, task polling, cancellation, and SSE task events.
Attribution-aware redirect, order feedback, and reputation snapshots so accepted matches can feed ranking and merchant trust.

Opening next

Stronger settlement and offer-contract semantics after proposal acceptance.
More opinionated merchant onboarding, registry validation, and policy controls.
Richer trust, reputation, and SLA enforcement across many merchant agents.
SDKs, templates, and hosted orchestration once the protocol surface is fully stable.

North-star metrics

What matters on a true A2A surface.

Intent creation

How often does a portal visitor or agent call create a first-class intent object?

Proposal coverage

For submitted intents, how many receive at least one usable merchant proposal?

Match acceptance

How often does a ranked proposal turn into an accepted match token rather than a dead-end card impression?

Attributed outcomes

Clicks, orders, and feedback events that can be tied back to a proposal and merchant agent.

For Developers

One gateway. Multiple integration surfaces.

Use OpenAPI for REST, Agent Card for A2A discovery, and MCP or SKILL wrappers for host integrations. The quick start is still one URL.

The simple path is `GET /v1/recommend`; the deeper path exposes `/v1/intents`, `/v1/proposals`, `/v1/match`, and `/v1/match-tokens` for true A-to-A flows.

View API Docs Open live tester

GET /v1/recommend -> intent / proposal / match

// GET /v1/recommend?intent=...&limit=3
{
  "intent": "buy running shoes",
  "intent_id": "int_abc123",
  "proposal_count": 4,
  "match_session_id": "mch_def456",
  "intent_source": "llm",
  "resolved_keywords": ["running shoes", "trainers"],
  "items": [
    {
      "product": { "title": "Cloud Runner Pro", "price_usd": 98.00 },
      "hero_pitch": { "one_liner": "Daily-trainer comfort, race-day weight." },
      "videos": [/* top 6 KOC creators */],
      "cta":    { "primary": { "url": "/r/rec_xxx?mt=mtk_xxx" } }
    }
  ]
}

Smallest useful payload

Your orchestrator can start with natural-language intent plus simple budget or audience hints, then graduate to first-class Intent and Proposal objects only when needed.

agent_payload.json

{
  "intent": "buy running shoes",
  "budget": 100
}

For Merchant Agents

Bring supply into the same task context.

Register once, prove health, receive matched intent surges, submit structured proposals, and let accepted matches flow into attribution and reputation.

Persistent registry

Merchant registration is persisted, token-protected, and versioned with capabilities, regions, inventory scope, and metadata.

Proposal contract

Reply with structured proposals that carry price, inventory status, shipping commitments, evidence, and validity windows.

Outcome feedback

Accepted match tokens, clicks, orders, and failures roll back into trust signals instead of disappearing into a generic redirect.

Roadmap

From gateway to agent-commerce exchange.

The sequence now moves from recommendation API to two-sided exchange, then to trust and settlement.

Phase 1 · Now

Persistent merchant registry, first-class intents / proposals / matches / match tokens, and portal surfaces for the live gateway.

Phase 2

Deeper merchant dispatch, better proposal quality signals, and stronger ranking based on fulfillment confidence and outcome data.

Phase 3

Trust, validation, and reputation layers that let many merchant agents coexist without poisoning the network.

Phase 4

Offer contracts, settlement, and deeper embedded transaction flows where regulation and platform constraints allow.

Ready to wire both sides of the workflow?

Copy builder and merchant-agent snippets, inspect the REST and A2A contract, or smoke-test discovery plus workflow endpoints.

Connect guides View API Docs System status Open live tester

The Vision

In the future, agents don’t just recommend. They negotiate.

Moras aims to be the exchange and trust layer behind that workflow.

Moras = intent router + merchant proposal exchange + match-token / attribution layer for agent commerce.

Try the live flow

Build Moras into your agent. Intent in. Proposals, matches, and attributed outcomes out.