canonical: https://jentic.com/apis/orbit.love/orbit # Orbit Love Orbit API Orbit is a community-management platform, and this API manages the members, activities, and organizations that make up a community workspace. An agent can list and create members, record activities against them, add notes and identities, read reports, and manage webhooks. It fits developer-relations and community teams that want to keep member records and engagement current without manual data entry. Most operations are scoped to a workspace by its slug. ## For AI agents Manage community members, activities, organizations, notes, and reports within an Orbit workspace. ## Scope Does not host community conversations itself. Use it to manage members, activities, organizations, notes, reports, and webhooks within an Orbit workspace. ## Capabilities - List and create members in a workspace - Record and read activities for members - Add notes and identities to members - List and read organizations and their members - Read workspace reports - Manage webhooks for a workspace ## Use cases ### Member Sync An agent keeps the community roster current by listing members with GET /{workspace_slug}/members and adding new ones with POST /{workspace_slug}/members. This lets a sign-up flow feed Orbit without manual entry. Example prompt: List members with GET /{workspace_slug}/members and add new ones with POST /{workspace_slug}/members ### Activity Logging A relations agent records engagement by posting to POST /{workspace_slug}/activities when a member does something noteworthy. This builds an activity history that reports can draw on. Example prompt: Record the engagement with POST /{workspace_slug}/activities for the member ### Engagement Reporting An agent reads GET /{workspace_slug}/reports to summarize how a community is doing and surface trends. This gives a team a current view without opening the dashboard. Example prompt: Read the summary with GET /{workspace_slug}/reports for the workspace ### Member Enrichment When new context arrives, an agent adds a note or identity to a member so the record stays complete. Notes and identity endpoints let it attach detail gathered from other systems. Example prompt: Attach context to the member with the notes and identities endpoints ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/workspaces` | List workspaces | | GET | `/{workspace_slug}/members` | List members in a workspace | | POST | `/{workspace_slug}/members` | Create a member | | POST | `/{workspace_slug}/activities` | Record an activity | | GET | `/{workspace_slug}/reports` | Read workspace reports | ## Key resources - **Members** — List, create, update, and enrich community members - **Activities** — Record and read member and workspace activities - **Reports and Webhooks** — Read workspace reports and manage webhooks ## Why Jentic - **Setup:** Wiring the Orbit API by hand means setting up bearer token authentication, learning its 33 operations across members, activities, organizations, and reports, and threading the workspace_slug through calls against https://app.orbit.love/api/v1. Through Jentic you install once, import the Orbit API from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** Because you run Jentic One yourself, you decide which Orbit operations the agent may call. Allow read-only access to members and reports, for example, and leave member creation, activity writes, and deletes out of the allowed set unless you add them. - **Credential handling:** Your Orbit token is stored once, encrypted, by your own Jentic One instance and injected on the Authorization header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent, such as 'add a new member to a workspace' or 'record an activity for a member', and Jentic returns the matching Orbit operation with its input schema so the agent calls the right endpoint. ## Related APIs - **Discourse API** — Discourse runs the forum where community conversations happen; Orbit tracks the members and their activity. - **Intercom API** — Intercom manages customer messaging and support; Orbit focuses on community members and engagement. - **Salesforce API** — Salesforce is the system of record for accounts; Orbit tracks community engagement around them. ## FAQ ### What can an AI agent do with the Orbit API? An agent can list and create members, record and read activities, add notes and identities, read organizations and reports, and manage webhooks. It covers the day-to-day of keeping a community workspace current. ### What authentication does the Orbit API use? The specification declares bearer token authentication, so each request carries the token in the Authorization header. Through Jentic that token is held by your own instance and set on the request at execution time. ### Are Orbit operations scoped to a workspace? Yes. Most endpoints take a workspace_slug in the path, so calls act on one workspace at a time. GET /workspaces lists the workspaces an agent can act on. ### Is there an MCP server for the Orbit API? You do not need a separate MCP server to use the Orbit API with an agent. Through Jentic One, the self-hosted execution layer, your agent calls the operations directly after you import them from the API Directory. Install Jentic One from github.com/jentic/jentic-one to run it yourself. ### How does my agent discover Orbit operations through Jentic? Agents search Jentic by intent, such as 'add a new member to a workspace', and Jentic returns the matching operation with its input schema. The agent then calls the right endpoint without reading the full reference. ### Can I limit what my agent is allowed to do with the Orbit API? Yes. Because you run Jentic One yourself, you decide which Orbit operations the agent may call. You can allow read-only access to members and reports, and leave member creation, activity writes, and deletes out of the allowed set unless you add them, so the agent acts only within the operations you permit.