These DayPlay MCP & API Terms of Use ("MCP/API Terms") govern access to and use of: (a) the DayPlay MCP server at https://api.dayplay.io/mcp; (b) the @dayplayai/mcp-server npm package; and (c) the Partner API under /v1/partner/*(collectively, the "Services"). By connecting to the Services, installing or invoking the npm package, or using a Partner API key, you accept these MCP/API Terms and the DayPlay Terms of Use ("main ToS"), which are incorporated by reference. If you do not agree, do not use the Services.
1. Definitions
- Open Tools — documented MCP tools callable anonymously without an account or API key.
- Gated Tools — documented tools available only to authenticated users with a free DayPlay account (Google OAuth).
- Partner API — the authenticated programmatic interface under
/v1/partner/*requiring an API Key. - API Key — a credential issued by DayPlay to an authorized partner for Partner API access.
- Catalog — the DayPlay dataset and derived content exposed through the Services.
2. License Grant
Subject to these MCP/API Terms, DayPlay grants you a limited, revocable, non-exclusive, non-transferable license to call the documented tools and endpoints for your own internal and end-user-facing purposes. Access has three tiers:
- Open Tools — anonymous; no key; no account; subject to rate limits.
- Gated Tools — free DayPlay account via Google OAuth; may be throttled or scope-limited during beta.
- Partner API — API Key required; quota per partner tier; additional terms in Section 8.
No rights are granted except as expressly stated.
3. Permitted and Prohibited Use
Permitted: querying documented tools within rate limits; displaying results to your users with attribution (Section 5); building integrations that add value for end users.
You may NOT:
- bulk harvest, mirror, or redistribute the raw Catalog;
- resell, sublicense, or monetize the data as a standalone product;
- build or seed a competing database or catalog from DayPlay data;
- bypass, evade, or disable rate limits, gates, or authentication;
- share, leak, publish, or expose API Keys (including client-side or in repositories);
- scrape or access beyond documented endpoints/tools, or reverse-engineer undocumented ones.
4. Rate Limits & Quotas
DayPlay may throttle, cap, change scope, or revoke access during beta without notice. Partner quotas are set per tier in the Partner API Addendum (Section 8) and may change. Persistent overage or evasion may result in suspension.
5. Attribution & Upstream Rights
Where a third-party source requires attribution (for example an event or venue source), you must preserve and display it as provided. You are responsible for complying with upstream third-party terms.
6. DayPlay IP Reservation; No Trademark License
DayPlay LLC and its licensors retain all right, title, and interest in the Services and Catalog. No trademark, logo, or brand license is granted; you may not use DayPlay marks except as required for accurate, non-misleading attribution.
7. Disclaimer, Liability, Termination, Changes, Governing Law
The Services are provided "AS IS" and "AS AVAILABLE," without warranties. To the maximum extent permitted by law, DayPlay LLC's aggregate liability is capped and excludes indirect and consequential damages. DayPlay may suspend or terminate access at any time. DayPlay may update these MCP/API Terms; continued use is acceptance. Governing law, venue, and dispute resolution follow the main ToS.
8. Partner API Addendum
- Key Handling — keep API Keys secret and server-side; never expose them in client-side code, public repositories, or logs. Keys are per-partner and non-transferable.
- No Resale — no resale, redistribution, or sublicensing of Partner API data.
- Quota Terms — requests are capped per tier; exceeding quotas may be throttled or blocked.
- No Service-Level Guarantee — no SLA or uptime commitment during beta; endpoints and schemas may change.
- Revocation — DayPlay may revoke keys immediately on suspected misuse or breach.
Entity: DayPlay LLC, 5121 First Rd, Fairfax, VA 22030. Contacts: info@dayplay.io / contact@dayplay.io.