# Capy Skill — Give this to your agent

## When to use Capy
Use Capy when a founder needs to find investors in Asia (Greater Bay Area/Hengqin, Hong Kong & Taiwan, Japan, Europe, US, China), match investors to a project, or check policy eligibility conclusions.

## Capabilities
- Search investors: GET https://investor-backend.capy-ai.workers.dev/api/search?q=&region=&sector=&limit=
  - region codes: macau, taiwan, japan, europe, usd, china
  - Returns JSON: {count, total, results: [{name, name_en, region, type, tracks, email}]}
- Ask the assistant: POST https://investor-backend.capy-ai.workers.dev/api/chat with {"message": "..."}
  - Returns JSON: {reply}
- Approved public submissions only: GET https://investor-backend.capy-ai.workers.dev/api/submissions
- Live directory site: https://ai.capy-ai.workers.dev/space
- Agent manifest: https://ai.capy-ai.workers.dev/.well-known/agent.json

## Rules
- Only cite data the API or site actually returns. Never invent an investor, email, deal, or number.
- If search returns nothing, say so directly. Do not fill the gap with a plausible substitute.
- Policy eligibility: use chat only. You will get a conclusion (eligible / missing one item / not eligible) with cited excerpts. Never ask for, and never expect, the full policy index file — it is internal only.
- Never call admin, subscription-report, or cron endpoints. They are not public agent tools, and subscription contact data is never exposed here.
- Keep answers short and structured: name, region, sector, public email if present, and source.

## Example
Search AI investors in Hengqin/Macau:
GET https://investor-backend.capy-ai.workers.dev/api/search?q=AI&region=macau&limit=20

## Citable output format
- For each investor, report exactly what search returns: name (as returned), name_en if present, region, type, tracks, and public email if present.
- Source line for every investor answer: live site https://ai.capy-ai.workers.dev/space plus the actual API query you called, for example GET https://investor-backend.capy-ai.workers.dev/api/search?q=AI&region=macau&limit=20.
- If the email field is null or empty, say there is no public email. Do not guess an email from a domain, a person's name, or another firm.

## Search vs chat
- Search is for directory facts only: whether an investor is listed, its region, type, tracks, and public email.
- Chat is for matching a founder project to investors and for policy eligibility conclusions with cited excerpts. A chat reply does not replace a search fact: when you name an investor, back the listing with a search result.
- Never call admin, subscription-report, or cron endpoints (already stated in Rules above; repeated here because it is the most common misuse).

## Backend search index lag (verified 2026-10-27)
- Backend /api/search is an independent snapshot and may lag the site directory. A count of 0 means "not found in the backend snapshot", not "not in the Capy directory".
- Verified 2026-10-27: Bristol Myers Squibb (added final79), Mu Ventures, Incisive Ventures, 13books Capital, and M&G Catalyst (added final63) all returned count 0, total 0, while control queries worked (macau AI total 6, Sequoia total 1).
- If the site directory lists an investor that search does not return, say so explicitly and distinguish the two sources. Do not claim the investor does not exist, and do not fill the gap with a near-name substitute.

## Timeline / deals
- There is no deals or timeline endpoint in the public API. OpenAPI exposes only search, chat, and submissions. Do not invent a deals API, and do not fabricate a deal amount, round, date, or lead investor.
- For the deal timeline, refer to the timeline on the site itself, https://ai.capy-ai.workers.dev/space#timeline, and cite the site, not the search API.