Developer / API Terms

By requesting or using an API key, registering an OAuth client, connecting an AI agent through the MCP server, installing the SDK, or otherwise calling the API, you agree to these Developer Terms. They apply whether you build for your own workspace or for other SkedCast users. If you accept on behalf of an organization, you represent that you are authorized to bind it. You must be at least 18 and able to form a binding contract.

In these Developer Terms: the “API” means the components described above; “Your Application” means the software, integration, script, or AI agent you build or operate using the API; “Developer Credentials” means API keys, OAuth client identifiers, and access or refresh tokens issued to you; an “End User” is a SkedCast user on whose behalf Your Application acts; and “End-User Data” is data you access or receive through the API, including data that originates from a connected third-party platform.

Subject to your continued compliance with these Developer Terms, we grant you a limited, revocable, non-exclusive, non-transferable, non-sublicensable license to access and use the API solely to build and operate Your Application’s interoperation with the Service. Every credential’s effective permission is the intersection of its granted scopes and the underlying member or End User’s role — a credential can never do more than the person it represents could already do, and a granted scope never escalates privilege. We reserve all rights not expressly granted.

You are responsible for all activity under your Developer Credentials and for keeping them confidential. API keys are secrets: keep them server-side, never embed them in a browser, mobile app, or public repository, and never share them. We store only a hashed form of each API key, so a raw key is shown once at creation. If a credential is exposed, rotate or revoke it immediately and notify us at [email protected]. We may rotate, suspend, or revoke a credential we reasonably believe is compromised, abused, or used in breach of these Developer Terms.

When Your Application acts on behalf of an End User, you must use our OAuth 2.1 authorization-code flow with PKCE and request only the scopes you need. You must clearly present to the End User who you are and what your Application does, honor the consent they grant, and stop using a token once it is revoked or the End User disconnects. You may not store, cache, or use End-User Data or tokens beyond what is necessary to provide the function the End User authorized, and you may not impersonate SkedCast or another developer. The MCP server is subject to the same authorization, scope, and acceptable-use rules as the rest of the API.

Your use of the API must comply with our Acceptable Use Policy. In addition, you must not:

• exceed, evade, or design around documented rate limits, quotas, scopes, or other technical or usage restrictions;
• probe, scan, or test the vulnerability of the API, or breach or circumvent any authentication, security, or access control;
• reverse engineer, decompile, or attempt to derive source code or non-public aspects of the API or Service, except where the law expressly permits it;
• sell, resell, lease, sublicense, or provide the API as a standalone product, or use it to build a service that substantially replicates or competes with SkedCast;
• use the API to send spam or unlawful, infringing, deceptive, or abusive content, to harvest data, or for any high-risk use where failure could lead to death, personal injury, or serious harm;
• misrepresent the source of requests, share or pool credentials across unrelated users, or create accounts or credentials by automated means to evade limits; or
• violate the developer, API, or platform terms of any connected third-party network, or fail to make AI-content and paid-partnership disclosures where a platform or the law requires them.

The API is rate-limited and subject to fair use. Current limits and the response headers that report your remaining quota are published in our developer documentation. You must read those headers and back off accordingly; you must not design Your Application to circumvent limits. We may throttle, queue, suspend, or adjust limits — including for a single developer — to protect the performance, integrity, and availability of the Service for everyone.

You may access End-User Data only with valid authorization and only to provide the function the End User asked for. You must protect End-User Data with appropriate technical and organizational measures, collect and retain the minimum necessary, and delete it when it is no longer needed, when the End User revokes access, or on request. You must handle personal data in accordance with applicable law and with our Privacy Policy and, where you act as our processor or sub-processor, our Data Processing Addendum. You must not sell End-User Data, use it for advertising or profiling, or use it to train models except as the End User has specifically authorized. You must maintain your own privacy notice describing how Your Application handles End-User Data.

End-User Data you receive through the API may originate from a connected third-party platform (for example X, Meta’s Facebook, Instagram, or Threads, YouTube, TikTok, LinkedIn, Pinterest, Bluesky, or Telegram). Your use of that data is also subject to the relevant platform’s developer and API terms and its limited-use requirements, as described on our Platform API Data Use & Compliance page. You are responsible for complying with those terms, and we may restrict or withdraw API features or data to meet a platform’s requirements or a change in its API.

The API is versioned in the path (for example, /v1) and evolves additively: we may add fields and endpoints at any time, so Your Application must tolerate new and unknown fields gracefully. We will ship breaking changes under a new version and aim to give reasonable advance notice and an overlap period before retiring a prior version. We may modify, deprecate, or discontinue any part of the API; you are responsible for keeping Your Application current. Error codes are stable identifiers — branch on the machine-readable code, not on human text.

The SDK and any features identified as beta, preview, or experimental are provided “as is”, may change or be withdrawn, and are not recommended for production unless we state otherwise. If we make the SDK available under a separate open-source or package license, that license governs your use of the SDK code; these Developer Terms continue to govern your use of the API it calls.

The API, SDK, documentation, and the Service are owned by Alpha Exotic Tech LLC or its licensors and are protected by intellectual-property laws. You retain ownership of Your Application. You may not use our name, logos, or trademarks except to make a truthful, non-misleading statement that Your Application works with SkedCast, and not in a way that implies our sponsorship or endorsement. If you send us feedback or suggestions, you grant us a perpetual, irrevocable, royalty-free license to use them without restriction.

You may stop using the API at any time and delete your credentials. We may suspend or revoke your access to the API or any credential — with or without notice where the circumstances warrant — if you breach these Developer Terms or the Acceptable Use Policy, if we reasonably suspect abuse or a security risk, or if a platform or the law requires it. On termination, your license ends and you must stop calling the API, delete your stored credentials, and delete or return End-User Data as required by our Data Deletion page. Provisions that by their nature should survive termination will survive.

The API is provided “as is” and “as available” without warranties of any kind, whether express, implied, or statutory, to the maximum extent permitted by law. We do not warrant that the API will be uninterrupted, error-free, secure, or backward-compatible, or that any request to a connected platform will succeed.

The limitations of liability and the liability cap set out in our Terms of Service apply to your use of the API and are incorporated here by reference. To the maximum extent permitted by law, neither party is liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenues, data, or goodwill, arising from your use of the API.

You will defend, indemnify, and hold harmless Alpha Exotic Tech LLCand its affiliates from any third-party claims, damages, and costs (including reasonable legal fees) arising out of Your Application, your use of the API, your handling of End-User Data, or your breach of these Developer Terms, the Acceptable Use Policy, or any platform’s terms.

These Developer Terms are governed by the laws of the State of Wyoming, USA, without regard to conflict-of-laws rules, and the governing-law and dispute-resolution provisions of our Terms of Service apply. Please raise any concern first by contacting [email protected].

We may update these Developer Terms from time to time. Material changes will be reflected by the “Last updated” date above and, where appropriate, communicated to you; continued use of the API after an update means you accept the revised Developer Terms. Questions can be sent to [email protected].