Third Eye Cyborg, LLC

    API Terms of Use

    Last updated: October 14, 2026

    API Terms of Use

    Effective June 1, 2026 Third Eye Cyborg, LLC Last updated June 5, 2026

    1. Overview

    These API Terms of Use ("API Terms") govern your access to and use of the Ascended Social Public API ("API"), including the REST endpoints and the Model Context Protocol (MCP) endpoint at https://developers.ascended.social/mcp. By creating an API key or making any API request, you agree to these API Terms in addition to our Website Terms of Service and Acceptable Use Policy.

    The API is provided by Ascended Social ("we", "us", "our"). If you access the API on behalf of an organisation, you represent that you have authority to bind that organisation to these terms.

    2. Access and API Keys

    Access to the API requires a valid API key. You may generate API keys in your account settings under Settings → Developer. Each key is personal to your account and must not be shared, transferred, or embedded in publicly accessible code, repositories, or client-side applications.

    You are solely responsible for all activity that occurs under your API key. If you believe your key has been compromised, revoke it immediately and generate a new one.

    3. Rate Limits and Quotas

    API keys are free and come with free usage limits shown in your dashboard. We may change limits.

    Exceeding your quota results in a 429 Too Many Requests response. We reserve the right to modify rate limits at any time with notice via our status page or email.

    4. Cosmos tools are not part of the Public API

    The authenticated Cosmos workspace may use RoxyAPI through Ascended Social's server-side integration. Cosmos tools are not public developer API endpoints, may be enabled or paused by Ascended Social, and may have separate account limits. Do not attempt to call, automate, scrape, or expose those internal routes. The RoxyAPI key is server-only and must never be placed in browser, mobile, extension, or published application code.

    3b. File Upload Quotas

    Media upload endpoints used by the Ascended Social apps (for attachments in Networks, including projects channels and their timesheet endpoints, and Whispers) are session-authenticated and are not currently part of the public developer API described in this document — they cannot be called with a Developer API key. When we open equivalent upload functionality to developer API keys, it will be subject to the file size limits and monthly storage quotas of the authenticated user's subscription tier, and this section will be updated accordingly.

    4. Permitted Uses

    You may use the API to:

    • Build applications that display or analyse public Ascended Social content
    • Integrate Ascended Social public data into third-party tools or dashboards
    • Conduct non-commercial research using publicly available data
    • Create bots or automated workflows that comply with our Acceptable Use Policy

    4b. Bot Platform

    Ascended Social provides a Bot Platform that allows developers to create automated agents ("Bots") that can be installed into Networks by their administrators. Projects channels are supported when the network's permissions model enables them. If you build, operate, or distribute a Bot, the following additional terms apply in addition to all other sections of these API Terms.

    • Token security. Bot tokens (bt_live_...) are equivalent to credentials. You must store them securely, never expose them in client-side code or public repositories, and revoke them immediately if compromised.
    • Transparency. Bots must not impersonate human users, platform staff, or other bots. Your bot's username and display name must make its automated nature reasonably clear to network members.
    • Installation consent. A Bot may only operate in a Network if a network owner or admin has explicitly installed it via the Network settings. You must not attempt to install your Bot in networks without explicit authorisation from a network admin.
    • Webhook security. If you configure a webhook URL, you are responsible for verifying the X-Ascended-Signature header on every inbound request using a constant-time comparison. Do not process payloads that fail signature verification.
    • Message volume. Bots are subject to the same per-user rate limits as human accounts and must not flood channels with automated messages. Workflows that generate sustained high message volumes must implement client-side rate limiting.
    • Data minimisation. Bots may only request the permission scopes necessary for their stated purpose. Member data accessed via members:read must not be stored beyond what is strictly necessary, shared with third parties, or used for profiling or targeting outside the bot's stated function.
    • Prohibited bot behaviours. Bots may not send spam or unsolicited messages, harvest member data beyond their declared purpose, exfiltrate content outside the platform, execute actions on behalf of users without their consent, or take any action that violates our Acceptable Use Policy.
    We reserve the right to revoke any Bot's installation access, suspend its tokens, or remove it from the Bot Directory without notice if it violates these terms, causes harm to users, or disrupts platform operations.

    4c. Bot Tokens & Automated Access

    Bot tokens are delegated credentials issued to bot operators. You are responsible for all requests made with your bot tokens, including actions performed by hosted infrastructure, contractors, or automation pipelines you control.

    • Issuance and scope. You must request only the minimum scopes needed for your bot's function and avoid broad or unnecessary access.
    • Operator responsibility. You are accountable for bot behavior, including content generation, slash-command execution, and webhook handling.
    • Prohibited automated uses. Automated scraping, data harvesting beyond declared purpose, coordinated spam, and impersonation are prohibited and may trigger immediate enforcement.
    • Revocation policy. Ascended Social may revoke bot tokens, remove installations, or disable bot access immediately when abuse, security risk, policy violations, or legal obligations require intervention.

    5. Prohibited Uses

    You may not use the API to:

    • Scrape, harvest, or mass-download data beyond normal API use patterns
    • Circumvent or attempt to bypass authentication, rate limits, or access controls
    • Access, store, or process data on behalf of another person without their consent
    • Use API responses to train machine learning models or AI systems without our written permission
    • Reproduce, resell, or redistribute Ascended Social data as a standalone data product
    • Engage in any use that violates our Acceptable Use Policy
    • Use the API in a manner that could damage, disable, or impair our infrastructure

    6. Data and Privacy

    The API returns only publicly available data. Personally identifiable information (PII) such as email addresses and phone numbers is excluded from all API responses. You must handle any data obtained via the API in accordance with applicable privacy laws, including the GDPR and CCPA.

    Event-related API access is intentionally privacy-scoped: private events and seances are excluded from public developer interfaces, and draft or cancelled events are not returned in public discovery endpoints.

    You may not use API data to identify, contact, or target individual users for marketing, advertising, or profiling purposes without their explicit consent.

    6b. Soul State and Presence API

    The Soul State system exposes a user's current live presence tag via authenticated API endpoints. The seven Soul States are: Sleep (offline), Dream (REM / quiet-focus mode), Lucid (online, idle), Experiencing (consuming content), Sharing (creating or live), Connecting (in a call), and Meditating (in a focused practice session).

    • Privacy-scoped reads. Soul State and presence data is only returned for users who have not set their presence to invisible or private. Requests for users with private presence settings return null for the state field — never an error.
    • No polling at high frequency. Presence endpoints are subject to standard rate limits. High-frequency polling (more than once per 10 seconds per user) is prohibited and will be rate-limited.
    • No presence tracking or profiling. You may not store, aggregate, or analyse Soul State data to build activity profiles, infer behavioural patterns, or target users for advertising or outreach.
    • Dream mode must be respected. If a user's Soul State is dream, your application must not initiate call requests, send automated messages, or otherwise attempt to interrupt that user's quiet-focus session.
    • Write access. The PUT /users/me/dream-state endpoint allows the authenticated user to toggle REM mode programmatically. This endpoint may only be called on behalf of the authenticated user and not to alter another user's state.

    7. Attribution

    When publicly displaying content retrieved via the API, you must include a visible attribution such as "Powered by Ascended Social" or "Data from Ascended Social" with a link to ascended.social.

    8. Intellectual Property

    Ascended Social retains all intellectual property rights in the API, its responses, and the underlying platform. These API Terms do not grant you any ownership rights. User-generated content remains the property of its creators; your use of that content via the API is subject to the rights granted by those users to Ascended Social under our Terms of Service.

    9. Suspension and Termination

    We may suspend or revoke your API access at any time, with or without notice, if we determine that you have violated these API Terms, our Acceptable Use Policy, or any applicable law. We will make reasonable efforts to notify you before suspension unless we believe immediate action is necessary to protect our platform or users.

    10. Disclaimer of Warranties

    The API is provided "as is" without warranties of any kind. We do not guarantee that the API will be available, error-free, or uninterrupted. API response formats, endpoints, and rate limits may change at any time; we will provide advance notice of breaking changes where reasonably practicable.

    11. Limitation of Liability

    To the fullest extent permitted by applicable law, Ascended Social shall not be liable for any indirect, incidental, special, or consequential damages arising from your use of the API, including data loss, service interruptions, or errors in API responses.

    12. Changes to These Terms

    We may update these API Terms from time to time. Material changes will be communicated via the developer documentation site or by email to the address on your account. Continued use of the API after changes take effect constitutes acceptance of the revised terms.

    13. Contact

    Questions about these API Terms or your API access? Contact us at api@ascended.social.

    Questions: legal@thirdeyecyborg.com

    Powered by PolicyForge