Build with Aicoo + API

Aicoo lets your product give every user a useful AI operations layer: persistent context, notes, todos, scoped agent links, and tool-backed workflows. A common integration is simple: your app collects or syncs user context, creates an Aicoo agent link for the right audience, and lets people interact with that agent without exposing private workspace data.

This guide is the developer path. Use it to decide what you are building, then jump into the API reference for exact endpoints, request bodies, and examples.

How This Fits With the API Docs

• This page: product patterns, integration choices, and implementation checklist.
• API Reference: exact endpoint docs for API keys, OAuth, agent calls, OS endpoints, tools, heartbeat, and machine-readable specs.
• Machine-readable spec: use /docs/api/spec when generating SDKs, creating LLM ingestion files, or wiring an agent to the API surface.

In practice, start here, then keep the API Reference open while implementing.

API Map

Layer 1: Intro + API Key covers the fastest path to a working request: create an API key, send Authorization: Bearer <key>, and initialize a workspace.

Layer 2: Aicoo Agent covers conversational and agent-facing endpoints: chat, briefings, strategy generation, and planning outputs.

Layer 3: Aicoo OS + Tools covers the workflow layer: folders, notes, todos, memory, share links, conversations, tools, and heartbeat jobs.

OAuth / Connect Aicoo is the production authorization path when your app needs a user-approved "Connect Aicoo" flow instead of a manually pasted API key.

What You Can Add

Agent links give users a shareable Aicoo surface for a project, event, candidate profile, customer workflow, or team workspace. A link can be used by guests while still staying scoped to the context the user chose to share.

Context sync lets your backend write structured notes, project summaries, profiles, event metadata, or handoff packets into Aicoo so the agent can answer with current context.

OS APIs expose user-owned folders, notes, todos, memories, share links, and conversations so your product can build real workflows instead of a thin chatbot wrapper.

Tools and heartbeat let advanced integrations discover available tools, execute approved operations, and keep background workflows moving.

Integration Modes

API key mode is the fastest path for hackathons, pilots, and internal tools. The user creates an Aicoo API key, your backend stores it securely, and your server calls Aicoo on the user's behalf.

OAuth mode is the production "Connect Aicoo" path. Your app uses Aicoo's OpenID Connect discovery document, requests the scopes it needs, and receives user-authorized tokens.

Never put an Aicoo API key in frontend code, browser storage, or public repositories. Treat it like any other production secret.

Basic Flow

1. Get user authorization through an API key or OAuth.
2. Sync context into Aicoo as notes, folders, or structured memory.
3. Create a scoped share link for the workflow.
4. Let users or guests chat with the agent through the link or your own UI.
5. Read back outcomes such as conversations, notes, todos, or follow-up tasks.

Product Recipes

Hackathon Platform

For events like SEAHack, Aicoo can become the participant-facing team formation and project coordination layer.

• Create an event workspace or folder for each team.
• Sync team profile, project idea, track, mentor notes, and submission requirements.
• Create a share link for each team or project.
• Let mentors ask the team agent about progress, blockers, and required help.
• Read todos and notes back into the event dashboard for judging or support.

This works especially well when an event offers an Aicoo track: teams can either use Aicoo directly or build on top of Aicoo infrastructure.

Recruiting or Portfolio Flow

Aicoo can turn a candidate profile into a scoped agent that recruiters, collaborators, or mentors can query.

• Sync resume, portfolio links, project notes, preferred roles, and availability.
• Create a candidate-specific agent link.
• Let reviewers ask targeted questions without reading every document manually.
• Generate follow-up todos for interviews, references, or missing materials.

Customer Discovery or Partner Intake

Use Aicoo as a context-aware front desk for product, partner, or support flows.

• Sync product docs, pricing notes, onboarding steps, and partner constraints.
• Create a share link for the customer or partner.
• Capture questions and open issues as notes or todos.
• Review conversations to improve the underlying product workflow.

Implementation Checklist

• Store API keys and OAuth tokens only on the server.
• Use scoped context instead of dumping a full workspace into one link.
• Prefer structured notes and folders for anything your product will read later.
• Log which user initiated each Aicoo operation.
• Show users what context is being shared before creating a public or guest-facing link.
• Use /docs/api/spec when generating SDKs, agents, or LLM ingestion prompts.

Next Steps

Open the API reference for exact request formats and examples:

• Intro + API Key
• Aicoo Agent
• Aicoo OS + Tools
• OAuth / Connect Aicoo
• Machine-readable API spec