B2B API Terms of Service

These B2B API Terms of Service (the "API Terms") govern your access to and use of the Yoseri B2B API, including all endpoints served underhttps://app.yoseri.com/api/v1/b2b and any supporting webhooks, SDKs, or documentation (collectively, the "API"). The API Terms apply to all three commercial tiers — Builder, Platform, and Syndicate — and supplement our general Terms of Service. In the event of a conflict between the two documents with respect to the API, these API Terms control.

Clause 1 — Anti-Competition

Data obtained through the API, and any derivative work produced from that data (including aggregated picks, edge percentages, Kelly fractions, closing line value, true probabilities, and Monte Carlo outputs), may not be used to design, build, host, operate, or market a business-to-consumer (B2C) product that directly competes with Yoseri Terminal or any successor consumer product offered by Yoseri.

For the purposes of this clause, a product "directly competes" when it is offered to retail sports bettors as a subscription or freemium service and its primary marketed value proposition is substantially similar to Yoseri Terminal — e.g. a pre-match or live picks feed with edge / EV / Kelly sizing surfaced directly to end users.

The following uses are expressly permitted: internal analytics, model training, risk-management dashboards for syndicates and funds, editorial / media use with attribution, and B2B tooling where the end user is another business rather than a retail bettor. If you are unsure whether a planned product falls within this clause, contact legal@yoseri.com before going to market.

Clause 2 — No Raw Resale

Client may not resell, sublicense, redistribute, syndicate, or otherwise make the API data available to third parties in raw form. For the purposes of this clause, "raw form" includes but is not limited to:

• Verbatim or near-verbatim JSON responses from the API.
• CSV, Parquet, Arrow, or other structured exports of the API responses.
• Database dumps, backup files, or bulk data transfers derived from the API.
• Passthrough proxies or "white-box" API gateways that mirror Yoseri fields.

Every integration that exposes API data (even indirectly) to a third party must add substantial value on top of the raw response. "Substantial value" means a meaningful transformation, enrichment, visualisation, workflow, or editorial layer — not mere reformatting or field renaming. When in doubt, the rule of thumb is: a reasonable engineer examining the final product should not be able to reconstruct the original Yoseri payload field-for-field.

Clause 3 — Attribution

Clients on the Platform and Syndicate tiers must display a visible "Powered by Yoseri" attribution in any surface where API data is rendered to an end user. Acceptable placements include:

• A footer credit on pages or views that rely on API data.
• An "About" / "Data sources" section naming Yoseri.
• A small in-card badge when API data is rendered as a widget or embed.

The attribution must link back to yoseri.com and must not be obscured, hidden, or rendered in a colour that is not reasonably legible against its background.

Attribution may be waived only under a separate, signed white-label addendum executed by both parties. A verbal understanding, a sales email, or a support ticket does not constitute a white-label waiver.

Clause 4 — Audit & Monitoring

Yoseri reserves the right to audit Client's usage patterns of the API at any time, including (without limitation) per-endpoint call distributions, query patterns, geographic origin of traffic, caller fingerprints, and derivative products shipped by Client. Audits may be conducted remotely (log analysis, rate-limit telemetry, public-product inspection) or by written request for documentation.

Yoseri will provide written notice of suspension by email to the contact address on file within twenty-four (24) hours of the action and, where practicable, a summary of the evidence that triggered it. Client may appeal a suspension by emailing legal@yoseri.com within ten (10) business days.

Clause 5 — Syndicate NDA

Access to the Syndicate tier is conditional on the execution of a mutual Non-Disclosure Agreement ("NDA") with a term of two (2) yearsfrom the effective date, automatically renewed for successive one-year periods unless either party gives sixty (60) days' written notice of non-renewal.

The Syndicate NDA covers, at minimum, the following Confidential Information:

• The full posterior probability distributions returned by the Probability Engine Full endpoint (?full=true).
• The 95% confidence intervals and any other statistical bounds emitted alongside those distributions.
• The model metadata (model name, model version, devig method, fair-book counts, per-bookmaker odds snapshots, refresh timestamps) exposed to Syndicate callers.
• Any parameters, training data references, or algorithmic descriptions shared verbally, by email, or in Slack / shared drives during onboarding and support.

Breach of the Syndicate NDA — including publication, resale, or sharing of Confidential Information with personnel outside the need-to-know scope — is grounds for immediate termination of API access, forfeiture of pre-paid fees, and recovery of damages to the maximum extent permitted by law.

Clause 6 — Service Level Agreement

The following uptime commitments apply to the core B2B endpoints (/picks, /probabilities, /clv, /montecarlo, /webhooks), measured monthly and excluding planned maintenance announced at least seventy-two (72) hours in advance:

• Builder ($249/mo): best-effort. No SLA credits. Typical availability targets 99.0% but is not guaranteed.
• Platform ($799/mo): 99.5% monthly uptime. If monthly uptime falls below 99.5%, Client is entitled to a pro-rata service credit on the next invoice.
• Syndicate ($2,999/mo): 99.9% monthly uptime. Includes dedicated escalation contacts and priority incident handling. Service credits apply when uptime falls below 99.9%, calculated against the monthly fee.

Uptime is measured against successful HTTP responses (2xx or 3xx) to authenticated requests at the API edge. Errors attributable to Client (4xx responses, rate-limit rejections, malformed requests) and errors caused by upstream bookmaker outages beyond Yoseri's control are excluded from the calculation.

Service credits are the sole and exclusive remedy for SLA misses. To claim a credit, Client must submit a written request to billing@yoseri.com within thirty (30) days of the end of the affected month, including the affected dates, the observed error rate, and supporting logs.

Acceptable Use & Rate Limits

Each tier ships with a published daily call envelope (3,000 / 20,000 / unlimited for Builder, Platform, and Syndicate respectively). Every API response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers so Client can self-throttle. Requests that exceed the daily envelope receive a 429 Too Many Requests response and are not counted toward SLA uptime.

Changes to These Terms

Yoseri may update the API Terms from time to time. For Platform and Syndicate clients, any material change (defined as a change that restricts permitted use, reduces quotas, or alters attribution obligations) requires thirty (30) days' prior written notice. Builder-tier changes may take effect on fourteen (14) days' notice posted on this page.

Governing Law & Venue

These API Terms are governed by the laws of the Province of Ontario, Canada, without regard to its conflict-of-laws rules. Disputes arising out of or in connection with these API Terms shall be resolved exclusively in the courts of Toronto, Ontario, except where a signed enterprise agreement specifies a different venue.

Contact

For commercial questions (pricing, contracts, white-label): sales@yoseri.com.
For legal questions (these API Terms, NDA, audits): legal@yoseri.com.
For technical questions (rate limits, endpoints, webhooks): developers@yoseri.com.