Annex C — API & MCP Developer Terms

C1.1 This Annex C applies to you if you access the Platform programmatically, whether through:

• the Public API — the bidirectional integration used by POS and similar systems; or

• the MCP server — the Model Context Protocol surface exposed to external AI agents and assistants.

C1.2 It supplements the core Terms of Service. Where this annex conflicts with the core Terms, this annex prevails for Developers.

C1.3 If you integrate on behalf of a Restaurant Partner, both this annex and Annex B apply to that relationship, and you must have that restaurant's authorisation.

C2.1 Credentials. API access requires an API key (issued in the format `tt_live_…` or `tt_test_…`) and a separate signing secret. We store only a hash of your key; the full value is shown once at creation and cannot be recovered.

C2.2 Keep them secret. You must:

• store keys and signing secrets securely, and never in client-side code, public repositories, mobile app bundles or logs;

• use a separate key per integration and per environment;

• rotate credentials promptly if you suspect exposure; and

• notify us at security@taste-trail.com without undue delay if a credential is compromised.

C2.3 Responsibility. You are responsible for everything done with your credentials, whether or not you authorised it.

C2.4 Request signing. Requests must be signed as specified in our API documentation. We reject unsigned, mis-signed or replayed requests.

C2.5 Revocation. We may revoke credentials at any time where we reasonably believe they are compromised, misused, or used in breach of these Terms.

C3.1 Least privilege. Each key is granted a minimal set of scopes. You must request only the scopes your integration genuinely needs, and must not attempt to access endpoints outside them.

C3.2 Tenant isolation. Access is scoped per restaurant. You must not attempt to access, infer or correlate data belonging to a restaurant that has not authorised you.

C3.3 Restaurant authorisation. Before accessing a restaurant's data you must have that restaurant's informed authorisation, and must stop immediately if it is withdrawn.

C3.4 Acting on behalf. Where your integration performs actions on a restaurant's behalf — confirming a booking, changing a price — you must make clear to that restaurant what your integration does, and must not exceed what it authorised.

C3.5 No credential sharing. You must not share credentials with, or resell access to, a third party without our written consent.

C4.1 Read-only by design. The public MCP surface exposes discovery and information tools only — such as searching restaurants, retrieving menus, checking availability, checking dietary safety and retrieving events. It does not expose write operations, owner analytics, or restaurant operational tools.

C4.2 Do not attempt writes. You must not attempt to perform, or to induce the Platform to perform, any write operation through the MCP surface, nor attempt to reach tools outside the published public scope.

C4.3 Attribution. Where your agent surfaces Taste Trail data to an end user, you must make clear that the information comes from Taste Trail and must not present it as your own.

C4.4 Accuracy. Restaurant information is supplied by Restaurant Partners. You must not represent it as verified by you or by us, and must pass through any dietary or allergen caveats we provide.

C4.5 Allergen safety. Where your agent conveys dietary or allergen information, you must also convey that the user should confirm directly with the restaurant. Presenting our dietary data as a definitive safety guarantee is a material breach of these Terms.

C4.6 End users. You are responsible for your end users' compliance with these Terms to the extent they interact with Taste Trail data through your agent.

C4.7 Changes. The public tool surface may change. We will give reasonable notice of removals or breaking changes where practicable.

C5.1 Limits. Requests are rate-limited per key. Current limits are published in our API documentation and returned in `RateLimit-*` response headers. Exceeding a limit returns `429` with `Retry-After`.

C5.2 Back off. You must honour `Retry-After` and implement exponential backoff. Retrying aggressively against a `429` or `5xx` is a breach of this clause.

C5.3 Idempotency. Write requests must carry an `Idempotency-Key`. You must generate a new key per logical operation and must not reuse a key with a different payload.

C5.4 Efficiency. You must not poll more frequently than your use case genuinely requires. Where we offer webhooks for a change, use them instead of polling.

C5.5 No circumvention. You must not rotate keys, distribute requests across keys or IPs, or otherwise act to evade rate limits.

C5.6 Protective action. We may throttle, suspend or block an integration that threatens Platform stability, and will tell you why as soon as we reasonably can.

C6.1 Permitted use. You may use data obtained through the Platform only to provide the integration functionality the restaurant or end user expects.

C6.2 You must not:

• scrape, crawl, or bulk-extract data beyond what your authorised scopes provide;

• build or maintain a competing restaurant discovery, booking or listings database from our data;

• retain data longer than your integration needs, or after authorisation is withdrawn;

• sell, licence or redistribute our data to third parties;

• re-identify data we have aggregated or de-identified; or

• combine our data with other sources to profile individuals beyond the integration's purpose.

C6.3 AI and model training. You must not use data obtained through the Platform to train, fine-tune or evaluate a machine-learning model without our prior written consent. Using our data as live context to answer a user's question — which is what the MCP surface is for — is permitted and is not "training".

C6.4 Personal Information. Where your integration processes Personal Information:

• you must comply with POPIA and any other applicable data-protection law;

• you act as a responsible party for your own processing, or as an operator where you process solely on a restaurant's instructions;

• you must apply appropriate security safeguards; and

• you must notify us at security@taste-trail.com within 24 hours of becoming aware of a security compromise involving data obtained through the Platform.

C6.5 Caching. You may cache data for performance for a reasonable period, but must respect deletions and honour a restaurant's or user's withdrawal of authorisation promptly.

C7.1 You must maintain security practices appropriate to the sensitivity of the data, including encryption in transit, access control, and logging.

C7.2 You must not probe, scan or test the security of the Platform without our prior written permission.

C7.3 Responsible disclosure. If you discover a vulnerability, report it to security@taste-trail.com. Do not exploit it, access data beyond what is needed to demonstrate it, or disclose it publicly before we have had a reasonable opportunity to remediate. We will not pursue action against good-faith research conducted in line with this clause.

C7.4 You must not use the Platform to store, transmit or process malicious code.

C8.1 The API is versioned. We aim to avoid breaking changes within a version.

C8.2 Deprecation. Where we must make a breaking change or retire a version, we will give at least 90 days' notice to the contact address on your account, except where a shorter period is necessary for security or legal reasons.

C8.3 Additive changes — new fields, new endpoints, new optional parameters — may be made without notice. Your integration must tolerate unknown fields rather than failing on them.

C8.4 We may change rate limits, scopes or the MCP tool surface on reasonable notice.

C8.5 You must keep your integration current. We do not support indefinitely against deprecated versions.

C9.1 The API and MCP server are provided without a service level agreement unless we have separately agreed one in writing.

C9.2 We aim for high availability but do not guarantee it. Maintenance may cause interruption; we will give notice of planned maintenance where practicable.

C9.3 Developer support is available at developers@taste-trail.com on a reasonable-endeavours basis.

C9.4 Test credentials (`tt_test_…`) are provided for development. Do not use production credentials for testing, and do not use test credentials against live guest data.

C10.1 You may state that your product integrates with Taste Trail and may use our name and logo in accordance with any brand guidelines we publish.

C10.2 You must not:

• suggest that Taste Trail endorses, certifies or is responsible for your product;

• use our name in your product name, domain or app name without written consent; or

• use our marks in a way likely to cause confusion.

C10.3 We may list your integration in our directory and use your name and logo for that purpose. Either party may withdraw permission on written notice.

C11.1 You are responsible for your integration, including its correctness, security and effect on restaurants and end users.

C11.2 Indemnity. You indemnify Taste Trail (Pty) Ltd against any claim, loss, liability, cost or expense arising from:

• your integration's operation or failure;

• your breach of these Terms or any applicable law;

• your processing of Personal Information; or

• a claim by a restaurant or end user relating to your integration.

C11.3 Subject to clause 13.1 of the core Terms, our total aggregate liability to you is limited to the greater of fees you paid us in the preceding 12 months or ZAR 5,000. Where you pay us nothing, our liability is limited to ZAR 5,000.

C11.4 We are not liable for loss arising from your reliance on data supplied by Restaurant Partners, or from a change to the API made in accordance with clause C8.

C12.1 You may stop using the API or MCP server at any time and should revoke your credentials when you do.

C12.2 We may suspend or revoke access immediately and without notice where:

• credentials are compromised or misused;

• your integration threatens Platform stability, security or data integrity;

• you breach clause C6 (data use) or C7 (security); or

• we are required to by law.

C12.3 For other breaches we will give notice and a reasonable opportunity to remedy.

C12.4 On termination you must stop accessing the Platform, delete cached data obtained through it (except where law requires retention), and confirm deletion on request.

C12.5 Termination of a restaurant's subscription, or withdrawal of its authorisation, ends your right to access that restaurant's data immediately.