← Resources

// The Aicoo Track

Build with Aicoo.

Use AI agents, shared memory, team context, and Aicoo infrastructure to make your project smarter, more collaborative, and easier to continue after the event.

Aicoo Track prize

2000 HKD cash prize + 2000 USD in Aicoo credits, plus onboarding, API guidance, office hours, and judging support.

// Two Ways to Qualify

Use Aicoo, or Build on It

Both lightweight and deeply technical usage are welcome. The strongest submissions do both — use Aicoo during the hackathon and expose Aicoo-powered functionality inside the product itself.

Path A · Use Aicoo directly

Aicoo as your team’s collaboration layer.

  • ◆Create an Aicoo workspace or folder for the project.
  • ◆Keep project notes, decisions, assumptions, and tasks in Aicoo.
  • ◆Use agent links or shared agents to coordinate teammates.
  • ◆Run team formation, role assignment, ideation, or research in Aicoo.
  • ◆Post progress or final demos to Aicoo Square, if available for the event.
  • ◆Show how context persisted across the hackathon and improved the build.

Path B · Build on Aicoo infrastructure

Aicoo primitives inside your own product.

  • ◆Call Aicoo APIs from a backend service.
  • ◆Create or read notes, folders, tasks, or shared context.
  • ◆Use agent-to-agent communication patterns.
  • ◆Generate share links, agent links, or collaboration artifacts.
  • ◆Build domain workflows on Aicoo memory + coordination primitives.
  • ◆Back recruiting, discovery, research, CRM, matching, or ops agents with Aicoo.

// Get Building

Developer Entry Points

Start with the API-keymodel — it’s the fastest path for a hackathon. OAuth can come later, once your product needs public third-party authorization.

# Keep keys server-side. Never ship them to the client.
User frontend  ->  Team backend  ->  Aicoo API
  1. 1. Create or obtain an Aicoo account.
  2. 2. Generate or receive an API key per the event setup.
  3. 3. Store the key in backend environment variables only.
  4. 4. Call Aicoo APIs from a trusted backend or local server.
  5. 5. Keep frontends, screenshots, and public repos free of secrets.
  6. 6. Include sanitized logs or screenshots as proof.
aicoo.io/docs →aicoo.io/docs/api →

Primitives to reach for: agent identity & agent links · notes, folders & persistent context · tasks & workflow state · share links · agent-to-agent messaging · interaction transcripts. Aicoo isn’t just a chat surface — it’s a collaboration and agent infrastructure layer.

// Starting Points

Suggested Build Directions

AI-native Team Formation

Match participants on goals, skills, ideas, and working style — backed by persistent Aicoo profiles, agent links, and team notes.

Recruiting / Talent Matching

Candidates, founders, and organizers get Aicoo-backed profiles and agents; the product ranks fit, keeps notes, and coordinates outreach.

Customer Discovery / Sales CRM

A lightweight CRM where founders use Aicoo to remember conversations, summarize leads, assign follow-ups, and coordinate next steps.

Research Collaboration

A shared research workspace — collect sources, maintain assumptions, assign tasks, and preserve decisions across the hackathon.

Event Ops & Community Coordination

A SeaHack ops assistant that holds context, routes questions, tracks unresolved issues, and makes mentor/sponsor handoffs cleaner.

Agent-native Product Interfaces

Products where user-specific agents talk to each other, remember relationship context, and adapt to the person, team, or prior interaction.

// Show, Don't Tell

Submission & Proof

Devpost copy alone is not proof. Judges look for product behavior, code, logs, links, screenshots, or persistent Aicoo artifacts. Every submission needs a working demo, a clear explanation of where Aicoo appears, evidence of usage or integration, and a statement that no API keys are exposed.

Strong proof looks like

  1. 1

    GitHub repo showing backend integration with env-var API keys.

  2. 2

    Sanitized backend logs showing calls to Aicoo APIs.

  3. 3

    Screenshots of Aicoo notes, folders, tasks, or shared context.

  4. 4

    Agent links or share links used in the project.

  5. 5

    Evidence of agent-to-agent messages or collaboration flow.

  6. 6

    Before/after context persistence — Aicoo remembering project state.

  7. 7

    An Aicoo Square post or public project artifact, if available.

  8. 8

    A demo video of the actual Aicoo-powered workflow (not just a slide).

// The Rubric

How the Aicoo Track Is Judged

30%

Aicoo API / Infrastructure Usage

How meaningfully did the team use Aicoo primitives — notes, context, tasks, agents, share links, A2A, API calls? Central to the project, not decorative.

25%

Product Value

Does it solve a real problem for teams, communities, builders, companies, or users? Is the Aicoo integration tied to a clear benefit?

20%

Technical Execution

Does the demo work? Is the architecture reasonable? Are secrets handled correctly? Practical engineering discipline under hackathon constraints.

15%

Demo / Submission Completeness

Easy to judge: a demo, a repo or technical artifact, proof of Aicoo usage, and a clear explanation of the workflow.

10%

Aicoo-native Collaboration

Did the team use Aicoo to collaborate during the build — preserve decisions, coordinate roles, manage tasks, continue after the event?

Why this matters

The Aicoo Track makes SeaHack a live demonstration of how teams use agent-native infrastructure to collaborate faster, preserve context, and build products where AI agents are first-class participants.

Start with the API docs →