TOMO Partner Documentation Index

Audience: every TOMO partner (engineering team or business operator). This is your hub. Every other doc you need is one link away.

Start here

Never integrated with TOMO before? → QUICKSTART.md — how to apply, connect and test.

Ready to list? → apply at automobnxt.com/business. One form for every business — engineering teams and shops alike. Every application is reviewed by a person.

Already have an MCP server? → MCP_SPEC.md — what TOMO probes + what it expects you to return.

Already have a REST/GraphQL API but no MCP? → wrap it in a small MCP server with the official MCP SDK (see MCP_SPEC.md) — TOMO does not generate a wrapper for you. Then declare what you serve: MANIFEST_REFERENCE.md.

Building from scratch? → start with QUICKSTART.md, then MCP_SPEC.md.

The intent catalog (your operational manual)

TOMO has 99 intent specs. Each one maps to one of TOMO's 11 domains (table below). Read the catalog, find your intent, read its spec.

Master index

docs/intents/_INTENT_CATALOG.md — list of all 99 intents with a one-line description and the kind of business each fits (examples are not TOMO partners).

Canonical template

docs/intents/_TEMPLATE.md — the 13-section structure every intent spec follows.

Gold reference specs (read these even if your intent is different)

These three are the most complete examples. They show what depth looks like:

If your intent is not yet specced at full depth, use the closest gold-reference as your starting template + reach out to AUTOMOBNXT to commit a spec for your intent.

The contracts (what you implement)

These five docs are the load-bearing contracts. Every partner integrates against them:

Read all five before submitting a manifest. They're cross-referenced — each one points back to specifics in your intent's spec.

TOMO's 11 domains

compliance.* (verify_kyc, verify_rc_dl) is cross-cutting. Used electronics and furniture specs under marketplace.* sit outside the 11 domains today (Moto is vehicles only).

Read the intent catalog for the full intent-by-intent list.

The economics (what you make)

TOMO charges one platform commission on amount_inr for every successfully closed intent — and only then. The rate is the same for every business, from a solo driver to a large chain, and is stated in your listing agreement. There are no enterprise discounts, no volume tiers, no setup fees, no monthly subscriptions.

How you're billed: the customer pays you directly, on your own checkout — TOMO never collects or holds the money, so there is no settlement or payout from TOMO. TOMO records its fee for each completed order you report (amount_inr is your NET revenue — see COMPLETION_CONTRACT.md) and bills it to you separately. (planned: a partner dashboard with a ledger view — not built yet; today your setup is done with our team.)

The brand promise (what you sign up for)

When you join TOMO, you commit to:

1. Real data only. Every required field populated, no Lorem Ipsum, no AI photos, no placeholder ratings.
2. No paid placement. Ranking is TTBS-based, source-blind. No commission negotiations affect rank.
3. Honest signals. Self-rated TTBS values must reflect real positioning. Our team reviews them.
4. Transparent pricing. All fees included in total_inr upfront. No "resort fee at check-in" surprises.
5. Honored commitments. What you display at search/quote time is what the user pays + receives.
6. Real customer support. If you say you're available 24x7, a person must answer at all hours.

These are not suggestions. They're commitments TOMO will hold you to. Sustained violations are reviewed by the admin team and may result in your status being set to suspended or your access being revoked. (planned: automated three-strikes counter — not yet shipped.)

Common questions

Where does my brand show up?

Once your connection is approved, in every TOMO chat result you serve (partner results stay switched off until the first partner is approved). Your brand name and source label appear on the supplier badge — users tap your row, see your branded card, complete via your flow. TOMO is the orchestrator, not the merchant of record. You're the merchant. (planned: logo + customer support phone fields on the supplier badge — not yet shipped.)

Can I see my TTBS score?

No. Individual listing rank is opaque — this prevents gaming. Your CPC ledger (completed orders + commission earned, written by your webhook) is recorded server-side. (planned: partner-facing read view of the ledger and per-intent breakdown — not yet shipped.)

Can I integrate with TOMO and also keep my own app/website?

Yes. TOMO doesn't require exclusivity. You can serve users via your own surface + via TOMO. The commission is on TOMO-routed traffic only.

How do I get faster sandbox-to-prod review?

Our team reviews each submission by hand and writes back. We don't promise a review time yet. Complete submissions are the fastest to approve.

Operational support

Today (what's live)

• Email: krishna.gamasany@automobnxt.com — every partner message goes to the founder (best-effort, not contractually guaranteed yet)
• Setup with our team after approval — your keys, your manifest (checked on intent, domain, pricing.min/max, service_area) and the MCP probe
• HMAC-signed CPC webhooks — production signature verification; a timestamp older than 5 minutes is rejected (a repeat sent inside that window is not blocked yet)
• Manual admin review for compliance approval, status flips, and dispute resolution

Planned (not yet shipped — do not rely on these for go-live decisions)

• A self-serve partner dashboard: keys, manifest, verification, error log, ledger view
• Real-time SLA telemetry (latency p95, completion rate, dispute rate)
• 24x7 oncall channel + tiered escalation
• Automated three-strikes suspension + automatic SLA pool drop/rejoin
• Quarterly partner reviews + dedicated account managers above a volume threshold
• Structured user-vs-partner dispute flow with 5-business-day SLA

If any of these are critical to your decision to integrate, please email krishna.gamasany@automobnxt.com for a current build-status update before signing off.

Compliance + legal

• A live privacy policy URL is checked before production (for businesses in India, it must meet DPDP 2023).
• For businesses in India: GSTIN, and the domain licences your intent's spec names (FSSAI, RERA, RTO permits, etc.).

The full doc tree

docs/
├── PARTNER_INDEX.md              ← you are here
├── QUICKSTART.md                 ← apply, connect, test
├── MCP_SPEC.md                   ← MCP server expectations
├── MANIFEST_REFERENCE.md         ← every manifest field
├── COMPLETION_CONTRACT.md        ← closed-intent POST shape
├── WEBHOOK_SIGNING.md            ← HMAC-SHA256 examples
├── SANDBOX_TO_PROD_CHECKLIST.md  ← production gate
└── intents/
    ├── _TEMPLATE.md              ← canonical 13-section spec structure
    ├── _INTENT_CATALOG.md        ← all 99 intents catalogued
    ├── travel.book_hotel.md      ← gold reference
    ├── food.order_delivery.md    ← gold reference
    ├── mobility.book_intracity_ride.md  ← gold reference
    ├── mobility.book_intercity_ride.md
    ├── mobility.book_self_drive.md
    ├── mobility.book_two_wheeler_rental.md
    ├── mobility.book_airport_transfer.md
    ├── mobility.book_outstation_package.md
    ├── mobility.book_chauffeur_hourly.md
    ├── mobility.book_ev_with_charge_planning.md
    ├── mobility.book_recurring_commute.md
    ├── food.book_dine_in.md
    ├── food.book_dine_in_with_offer.md
    ├── food.subscribe_tiffin.md
    └── ... (every intent in the catalog has its spec)

Closing

The spec is the contract. Read the docs, apply, and we'll test your service with you inside TOMO before it goes live. Every application is reviewed by a person.

If you find a gap in the documentation — a missing intent spec, a vague field, a contradiction — email krishna.gamasany@automobnxt.com with the specific reference.

Built by AUTOMOBNXT · DPIIT Recognised Startup · 2026.