RISOS API & MCP Developer Terms

1. Access and credentials

API keys, MCP credentials, tokens, and secrets are confidential credentials associated with a RISOS account or workspace. You must protect them, use least-privilege scopes, rotate or revoke compromised credentials promptly, and avoid exposing secret values in public code, client-side bundles, logs, or other unauthorized locations.

2. Authorized use

You may use RISOS developer interfaces only for purposes permitted by the documentation, your plan, these terms, applicable law, and any source-platform restrictions that apply to returned data. Access to a developer interface does not grant a broader right to use underlying third-party data than RISOS itself has.

3. Plans, scopes, quotas, and technical limits

Developer access may be subject to plan entitlements, scopes, request limits, rate limits, concurrency limits, research-credit requirements, provider quotas, and security controls. You may not evade or bypass those limits. Limits may change to protect reliability, security, provider compliance, or service integrity, subject to any separate written commitment that expressly applies.

4. End-user applications

If your application serves other users, you are responsible for appropriate end-user terms, privacy disclosures, permissions, and security for your application. You must not represent your application as owned, endorsed, or operated by RISOS unless we have expressly authorized that representation.

5. Data delivery and source restrictions

RISOS may deliver raw evidence, references, hydrated data, derived intelligence, or no raw payload at all depending on the source policy and delivery channel. A reference-only or restricted response is an intentional policy boundary. You may not reconstruct restricted source payloads, use another endpoint to defeat a restriction, or retain/export source data beyond the applicable provider rules.

6. AI and MCP integrations

MCP clients and other AI integrations must operate within the scopes and permissions granted to their credentials. You are responsible for configuring approval, publication, deletion, spending, and other safeguards appropriate to your client. The AI Terms apply to model-assisted use, and the Acceptable Use Policy applies to all developer activity.

7. Security

You must use reasonable security controls for developer credentials and downstream applications, including secure secret storage, transport security, least privilege, access revocation, and prompt response to compromise. Do not share a browser session cookie or third-party provider credential with an MCP client when a RISOS API key is the intended authentication mechanism.

8. Prohibited uses

You may not use developer interfaces to violate law or rights, conduct unauthorized surveillance, misuse restricted data, scrape or circumvent a source platform, bypass user permissions, interfere with RISOS, evade billing or rate limits, create deceptive affiliation, distribute malware, or recover data or capabilities that RISOS intentionally restricts.

9. Monitoring and enforcement

RISOS may process usage, request, rate-limit, security, and audit metadata to secure developer access, investigate abuse, enforce limits, support users, and maintain reliability. We may rate limit, rotate, revoke, or suspend credentials when reasonably necessary for those purposes or to comply with provider requirements or law.

10. Changes, versions, and deprecation

APIs and MCP tools may evolve. Versioning, release notes, and documentation describe the currently supported contract. Unless a separate written agreement states a specific notice period, these terms do not create a guaranteed deprecation window.

11. Ownership and branding

RISOS APIs, MCP tools, documentation, software, names, logos, and related technology remain RISOS property or the property of applicable licensors. These terms do not grant trademark or branding rights except as expressly permitted in writing or documentation.

12. Support and service levels

Developer support and availability are provided according to the applicable plan and documentation. No uptime or service-level commitment applies unless RISOS expressly agrees to it in a separate written agreement.

13. Termination

When developer access ends, you must stop using revoked credentials and delete secret values that are no longer authorized. Retention or deletion of data obtained through RISOS remains subject to the Terms, Privacy Policy, source-platform requirements, and any applicable business agreement.

14. Contact

Developer-policy questions can be sent to hello@risos.co. Technical documentation is available at docs.risos.co.