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 — zero to first call in 30 seconds.

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? → MANIFEST_REFERENCE.md — declare your offering via the manifest editor.

Building from scratch? → start with QUICKSTART.md, then the reference implementations (forthcoming):

• tomo-partner-node-starter
• tomo-partner-python-starter
• tomo-partner-go-starter

The intent catalog (your operational manual)

TOMO has 100 intents catalogued across 9 user-facing domains. Each intent has a complete spec at full depth. Read the catalog, find your intent, read its spec.

Master index

docs/intents/_INTENT_CATALOG.md — list of all 100 intents with one-line description and existing partner exemplars.

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.

The 9 user-facing domains

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

The economics (what you make)

TOMO charges 10% on amount_inr for every successfully closed intent. Same rate for solo drivers, kirana stores, OYO chains, MakeMyTrip aggregators. There are no enterprise discounts, no volume tiers, no setup fees, no monthly subscriptions.

Settlement: monthly. Last day of each calendar month, TOMO computes:

your_payable = sum(amount_inr) - sum(commission_inr) - sum(refund_adjustments)

NEFT/IMPS to your registered account on the 5th of the following month.

Real-time accrual visible in your Tier 1 dashboard. No invoices to chase. No human-touch finance loop. The rate is locked in your sandbox terms — no renegotiations.

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. TOMO audits.
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 claim 24x7, a human responds within 5 min during all hours. TOMO field-tests.

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?

In every TOMO chat result you serve. 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 10% commission is on TOMO-routed traffic only.

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

Submit a complete checklist on first try. The compliance review window is 24-72h depending on submission completeness. Incomplete checklists trigger revisions, restarting the clock. The fastest reviews come from partners that pass everything on first submission.

Operational support

Today (what's live)

• Email: partners@automobnxt.com — partner support inbox (response target: best-effort, not contractually guaranteed yet)
• Manifest validation at submission — server-side check on intent, domain, pricing.min/max, service_area
• HMAC-signed CPC webhooks — production signature verification with 5-minute replay protection
• Manual admin review for compliance approval, status flips, and dispute resolution

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

• Sandbox dashboard error log viewer (probe failures, malformed responses, structured reasons)
• In-dashboard partner chat / Help button
• Real-time SLA telemetry (latency p95, completion rate, dispute rate) on partner dashboard
• 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 partners@automobnxt.com for a current build-status update before signing off.

• Partner-disadvantageous resolutions impact your dispute_rate metric — sustained > 2% triggers re-review

Compliance + legal

• DPDP 2023 compliance is mandatory. Your privacy policy URL is verified at sandbox-to-prod.
• GSTIN required for tax invoicing.
• Domain-specific licenses (FSSAI, RERA, RTO permits, etc.) per your intent's spec.
• Anti-money-laundering checks on settlement amounts > ₹50,000 (PMLA compliance).
• All terms of service in docs/PARTNER_TERMS.md (forthcoming).

Reference implementations (forthcoming)

We're shipping starter repos for the three most common languages. Each implements one intent end-to-end with all required fields populated. Use as scaffolding for your own integration:

• tomo-partner-node-starter — TypeScript + Express + MCP SDK
• tomo-partner-python-starter — Python + FastAPI + mcp-python-sdk
• tomo-partner-go-starter — Go + net/http + custom JSON-RPC

Distributed via secure download to approved partners. Email partners@automobnxt.com to request access.

The full doc tree

docs/
├── PARTNER_INDEX.md              ← you are here
├── QUICKSTART.md                 ← zero to first call
├── 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 100 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
    └── ... (more intents being added — see catalog for status)

Closing

The spec is the contract. TOMO does not gate on relationships, sales calls, or quarterly reviews. Read the docs, implement the contract, pass the checklist, ship.

If you find a gap in the documentation — a missing intent spec, a vague field, a contradiction — email docs@automobnxt.com with the specific reference. We treat doc bugs as P1.

Built by AUTOMOBNXT · DPIIT Recognised Startup · 2026.