# API Reference
Source: https://docs.colosseum.com/copilot/api-reference

Complete endpoint documentation, auth, rate limits, and curl examples for the Copilot API

All endpoints are prefixed with your `COLOSSEUM_COPILOT_API_BASE` (default: `https://copilot.colosseum.com/api/v1`).

All requests require a Bearer token:

```bash theme={null}
-H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT"
```

## Rate limits

All limits are per-user (keyed by your Colosseum account). Exceeding a limit returns `429` with a `Retry-After` header.

| Category           | Limit       | Applies to                             |
| ------------------ | ----------- | -------------------------------------- |
| Search             | 30 req/min  | `/search/projects`, `/search/archives` |
| Analysis           | 10 req/min  | `/analyze`, `/compare`                 |
| Concurrency        | 2 in-flight | All data endpoints                     |
| Source suggestions | 5 req/hr    | `/source-suggestions`                  |
| Feedback           | 10 req/hr   | `/feedback`                            |

When rate limited (429), honor the `Retry-After` header. Most agent runtimes handle this automatically.

***

## Endpoints

### GET /colosseum\_copilot/status

Auth pre-flight check. Call this first to verify your token is valid before making other API calls.

```bash theme={null}
curl "$COLOSSEUM_COPILOT_API_BASE/status" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT"
```

**Response:**

| Field           | Type    | Description                                  |
| --------------- | ------- | -------------------------------------------- |
| `authenticated` | boolean | Whether the token is valid                   |
| `expiresAt`     | string  | ISO date when the token expires              |
| `scope`         | string  | Token scope (e.g., `colosseum_copilot:read`) |

***

### GET /colosseum\_copilot/filters

Fetch available filters and canonical hackathon chronology. Use to translate hackathon or track names into valid slugs/keys before searching, and to get `startDate` values for chronology-sensitive answers.

```bash theme={null}
curl "$COLOSSEUM_COPILOT_API_BASE/filters" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT"
```

**Response includes:**

* `tracks[]`: `{ key, name, hackathonSlug, projectCount }`
* `hackathons[]`: `{ slug, name, startDate, projectCount, winnerCount }` — ordered chronologically (oldest first)
* `acceleratorBatches[]`: `{ key, name, companyCount }`
* `prizeTypes[]`: prize category names
* `prizePlacements[]`: placement ranks
* `problemTags[]`: `{ tag, count }` (top 25 by frequency)
* `solutionTags[]`: `{ tag, count }` (top 25 by frequency)
* `primitives[]`: `{ tag, count }` (top 25 by frequency)
* `techStack[]`: `{ tag, count }` (top 25 by frequency)
* `targetUsers[]`: `{ tag, count }` (top 25 by frequency)
* `clusters[]`: `{ key, label, projectCount }` (key format `v<N>-c<N>`)
* `archiveSources[]`: `{ key, label, documentCount? }` (`documentCount` is optional)

***

### POST /colosseum\_copilot/search/projects

Primary similarity search for hackathon projects.

```bash theme={null}
curl -X POST "$COLOSSEUM_COPILOT_API_BASE/search/projects" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "privacy wallet for stablecoin users",
    "limit": 10,
    "filters": {
      "winnersOnly": false,
      "acceleratorOnly": false
    }
  }'
```

**Recommended defaults:** `limit` 8–12, `includeFacets` false.

**Request parameters:**

| Param                | Type      | Default | Description                                                                     |
| -------------------- | --------- | ------- | ------------------------------------------------------------------------------- |
| `query`              | string    | `""`    | Natural language query (optional, max 500 chars; omit for filter-only browsing) |
| `hackathons`         | string\[] | -       | Filter by hackathon slugs, max 10 (e.g., `["cypherpunk", "breakout"]`)          |
| `trackKeys`          | string\[] | -       | Filter by track keys, max 10 (format `<hackathonSlug>/<trackSlug>`)             |
| `limit`              | int       | 10      | Max results to return (max 25)                                                  |
| `offset`             | int       | 0       | Pagination offset (applied after ranking)                                       |
| `diversify`          | boolean   | true    | Cross-hackathon diversity ranking. Set `false` for narrow deep-dives            |
| `includeFacets`      | boolean   | false   | Enable facet computation (adds overhead)                                        |
| `includeDiagnostics` | boolean   | false   | Include search diagnostics in response                                          |

**Filter parameters** (`filters` object):

| Param                  | Type      | Description                                                 |
| ---------------------- | --------- | ----------------------------------------------------------- |
| `winnersOnly`          | boolean   | Only prize-winning projects                                 |
| `acceleratorOnly`      | boolean   | Only accelerator portfolio companies                        |
| `acceleratorBatchKeys` | string\[] | Specific batches, max 10 (format `accelerator/<batchSlug>`) |
| `prizePlacements`      | int\[]    | Prize placement ranks                                       |
| `prizeTypes`           | string\[] | Prize categories, max 10                                    |
| `isUniversityProject`  | boolean   | University-affiliated projects                              |
| `isSolanaMobile`       | boolean   | Solana Mobile projects                                      |
| `techStack`            | string\[] | Tech stack tags, max 10                                     |
| `primitives`           | string\[] | Primitive/protocol tags, max 10                             |
| `problemTags`          | string\[] | Problem domain tags, max 10                                 |
| `solutionTags`         | string\[] | Solution approach tags, max 10                              |
| `targetUsers`          | string\[] | Target user segments, max 10                                |
| `clusterKeys`          | string\[] | Cluster keys, max 10 (format `v<N>-c<N>`)                   |

Discover valid filter values via `GET /filters`.

**Facet parameters:**

| Param       | Type      | Default | Description                                                                                                                                                                          |
| ----------- | --------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `facets`    | string\[] | -       | Dimensions: `hackathons`, `tracks`, `prizes`, `problemTags`, `solutionTags`, `primitives`, `techStack`, `clusters`. If omitted and `includeFacets=true`, all dimensions are computed |
| `facetTopK` | int       | 8       | Max buckets per dimension (1–20)                                                                                                                                                     |

**Response:**

| Field            | Type      | Description                                                         |
| ---------------- | --------- | ------------------------------------------------------------------- |
| `results`        | object\[] | Array of project results (see below)                                |
| `filtersApplied` | object    | `{ hackathons?: string[], trackKeys?: string[], filters?: object }` |
| `totalFound`     | int       | Total matching projects                                             |
| `hasMore`        | boolean   | Whether more results are available                                  |
| `facets`         | object?   | Facet buckets by dimension (only present when `includeFacets=true`) |
| `diagnostics`    | object?   | Search diagnostics (only present when `includeDiagnostics=true`)    |

**Result object** (`results[]`):

| Field         | Type      | Nullable | Description                                                                               |
| ------------- | --------- | -------- | ----------------------------------------------------------------------------------------- |
| `slug`        | string    |          | Project slug                                                                              |
| `name`        | string    |          | Project name                                                                              |
| `oneLiner`    | string    | yes      | Short project description                                                                 |
| `similarity`  | number    |          | Match score                                                                               |
| `hackathon`   | object    |          | `{ name, slug, startDate }`                                                               |
| `tracks`      | object\[] |          | `[{ name, key }]`                                                                         |
| `links`       | object    |          | `{ github, demo, presentation, technicalDemo, twitter, colosseum }` (all fields nullable) |
| `evidence`    | string\[] |          | Short snippets showing why this matched (max 2)                                           |
| `prize`       | object    | yes      | `{ type, name?, placement?, amount?, trackName? }` (inner fields nullable)                |
| `metrics`     | object    |          | `{ likesCount, commentsCount, updatesCount }`                                             |
| `team`        | object    |          | `{ count }`                                                                               |
| `crowdedness` | int       | yes      | Cluster size as a crowdedness proxy                                                       |
| `tags`        | object    | yes      | `{ problemTags[], solutionTags[], primitives[], techStack[], targetUsers[] }`             |
| `cluster`     | object    | yes      | `{ key, label }`                                                                          |
| `accelerator` | object    | yes      | `{ companySlug?, companyName?, batchKey, batchName }` (companySlug/companyName nullable)  |

**Facet bucket shape:** `{ key, label, count, sampleProjectSlugs[] }`

**Diagnostics object** (when `includeDiagnostics=true`):

| Field                  | Type    | Description                               |
| ---------------------- | ------- | ----------------------------------------- |
| `modeUsed`             | string  | `vector`, `text`, `hybrid`, or `filters`  |
| `fallbackUsed`         | boolean | Whether a fallback search tier was used   |
| `fallbackReason`       | string? | Reason for fallback (if applicable)       |
| `vectorCandidates`     | int     | Candidates from vector search             |
| `textCandidates`       | int     | Candidates from text search               |
| `tagCandidates`        | int     | Candidates from semantic tag search       |
| `diversityDropped`     | int     | Results removed by diversity filter       |
| `totalFoundIsEstimate` | boolean | Whether `totalFound` is an estimate       |
| `effectiveFilters`     | object  | Filters actually applied after resolution |
| `queryExpanded`        | string  | Query after synonym expansion             |

**Score interpretation:** Scores reflect hybrid RRF fusion across vector, text, and semantic tag channels. Use relative ranking within a result set rather than absolute thresholds.

***

### POST /colosseum\_copilot/search/archives

Search archival documents for conceptual precedents. Auto-cascades through tiers (vector → chunk text → document text) when a tier returns no results.

```bash theme={null}
curl -X POST "$COLOSSEUM_COPILOT_API_BASE/search/archives" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "prediction markets governance",
    "limit": 5,
    "maxChunksPerDoc": 2
  }'
```

**Recommended defaults:** `limit` 4–6, `maxChunksPerDoc` 2, `minSimilarity` 0.2.

**Request parameters:**

| Param              | Type      | Default | Description                                                                                                                                                 |
| ------------------ | --------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `query`            | string    | -       | Search query, **required** (min 1, max 500 chars). 3–6 focused keywords recommended                                                                         |
| `sources`          | string\[] | -       | Filter by source keys, max 20. Use `GET /filters` for valid values                                                                                          |
| `limit`            | int       | 5       | Max documents returned (max 10)                                                                                                                             |
| `offset`           | int       | 0       | Pagination offset (per document, not per chunk)                                                                                                             |
| `maxChunksPerDoc`  | int       | 2       | Chunks per document (min 1, max 4). Up to `maxChunksPerDoc` chunks per document in `vector`/`chunk_text` tiers; `doc_text` returns one snippet per document |
| `maxDocsPerSource` | int       | 3       | Cap results from any single source (0 for unlimited, max 10)                                                                                                |
| `intent`           | string    | `docs`  | `docs` for precision, `ideation` for broader recall                                                                                                         |
| `minSimilarity`    | float     | 0.2     | Minimum cosine similarity (0–1). Lower for niche queries                                                                                                    |

**Response:**

| Field            | Type      | Description                                                        |
| ---------------- | --------- | ------------------------------------------------------------------ |
| `results`        | object\[] | Array of archive results (see below)                               |
| `filtersApplied` | object    | `{ sources?: string[] }`                                           |
| `searchTier`     | string    | Which tier produced results: `vector`, `chunk_text`, or `doc_text` |
| `totalFound`     | int       | Total matching documents                                           |
| `totalMatched`   | int       | Total matched before pagination                                    |
| `hasMore`        | boolean   | Whether more results are available                                 |

**Result object** (`results[]`):

| Field         | Type          | Nullable | Description                        |
| ------------- | ------------- | -------- | ---------------------------------- |
| `documentId`  | string (UUID) |          | Archive document identifier        |
| `title`       | string        |          | Document title                     |
| `author`      | string        | yes      | Document author                    |
| `source`      | string        |          | Source key                         |
| `url`         | string        | yes      | Document URL                       |
| `publishedAt` | string        | yes      | ISO date string                    |
| `similarity`  | number        |          | Cosine similarity score            |
| `snippet`     | string        |          | Relevant excerpt from the document |
| `chunkIndex`  | int           |          | Chunk position within the document |

**Score interpretation:** Similarity above 0.4 is a strong topical match. 0.2–0.4 is worth reading but verify relevance. Below 0.2 is usually tangential. These thresholds apply to `vector` tier results. For `chunk_text` and `doc_text` tiers, prioritize snippet relevance over score magnitude.

**Query tips:**

* Keep to 3–6 focused keywords. Too short is vague; too long dilutes embedding similarity.
* If results are all pre-2010 for a modern query, re-query with ecosystem-specific terms.
* If empty, try conceptual synonyms (e.g., `"prediction markets"` → `"futarchy"`).

***

### GET /colosseum\_copilot/archives/:documentId

Fetch a paged archive document slice.

```bash theme={null}
curl "$COLOSSEUM_COPILOT_API_BASE/archives/DOCUMENT_UUID?offset=0&maxChars=8000" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT"
```

**Parameters:**

| Param        | Type          | Default | Description                                                |
| ------------ | ------------- | ------- | ---------------------------------------------------------- |
| `documentId` | string (UUID) | -       | Archive document identifier (**required**, path parameter) |
| `offset`     | int           | 0       | Character offset to start from (min 0)                     |
| `maxChars`   | int           | 8000    | Maximum characters to return (min 200, max 20000)          |

Use `offset` + `maxChars` to page through long documents. Check `hasMore` and use `nextOffset` for the next page.

**Response:**

| Field         | Type          | Nullable | Description                                          |
| ------------- | ------------- | -------- | ---------------------------------------------------- |
| `documentId`  | string (UUID) |          | Archive document identifier                          |
| `title`       | string        |          | Document title                                       |
| `author`      | string        | yes      | Document author                                      |
| `source`      | string        |          | Source key                                           |
| `url`         | string        | yes      | Document URL                                         |
| `publishedAt` | string        | yes      | ISO date string                                      |
| `content`     | string        |          | Document content slice                               |
| `restricted`  | boolean       |          | Whether content is truncated due to licensing        |
| `offset`      | int           |          | Starting character offset of this slice              |
| `maxChars`    | int           |          | Requested max characters                             |
| `totalChars`  | int           |          | Total document length in characters                  |
| `nextOffset`  | int           | yes      | Offset for the next page (`null` if no more content) |
| `hasMore`     | boolean       |          | Whether more content is available                    |

***

### GET /colosseum\_copilot/projects/by-slug/:slug

Fetch full project details by slug.

```bash theme={null}
curl "$COLOSSEUM_COPILOT_API_BASE/projects/by-slug/your-project-slug" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT"
```

Use for 1–2 top results when evidence from search results is insufficient.

**Response:**

| Field         | Type      | Nullable | Description                                                                                                              |
| ------------- | --------- | -------- | ------------------------------------------------------------------------------------------------------------------------ |
| `slug`        | string    |          | Project slug                                                                                                             |
| `name`        | string    |          | Project name                                                                                                             |
| `description` | string    | yes      | Full project description                                                                                                 |
| `oneLiner`    | string    | yes      | Short project description                                                                                                |
| `hackathon`   | object    |          | `{ name, slug, startDate }`                                                                                              |
| `tracks`      | object\[] |          | `[{ name, key }]`                                                                                                        |
| `links`       | object    |          | `{ github, demo, presentation, technicalDemo, twitter, colosseum }` (all fields nullable)                                |
| `team`        | object    |          | `{ count, members[] }` where each member has `{ displayName?, username?, githubHandle?, twitterHandle? }` (all nullable) |
| `isWinner`    | boolean   |          | Whether the project won a prize                                                                                          |
| `accelerator` | object    | yes      | `{ companySlug?, companyName?, batchKey, batchName }` (companySlug/companyName nullable)                                 |
| `createdAt`   | string    |          | ISO date string                                                                                                          |
| `tags`        | object    | yes      | `{ problemTags[], solutionTags[], primitives[], techStack[], targetUsers[] }`                                            |
| `cluster`     | object    | yes      | `{ key, label }`                                                                                                         |
| `metrics`     | object    | yes      | `{ likesCount, commentsCount, updatesCount }`                                                                            |
| `prize`       | object    | yes      | `{ type, name?, placement?, amount?, trackName? }` (inner fields nullable)                                               |

***

### Cohort definition

The `/analyze` and `/compare` endpoints accept a shared cohort definition to scope which projects are included:

| Field                  | Type      | Description                                                 |
| ---------------------- | --------- | ----------------------------------------------------------- |
| `hackathons`           | string\[] | Filter by hackathon slugs                                   |
| `trackKeys`            | string\[] | Filter by track keys (format `<hackathonSlug>/<trackSlug>`) |
| `winnersOnly`          | boolean   | Only prize-winning projects                                 |
| `acceleratorOnly`      | boolean   | Only accelerator portfolio companies                        |
| `acceleratorBatchKeys` | string\[] | Specific batches (format `accelerator/<batchSlug>`)         |
| `prizePlacements`      | int\[]    | Prize placement ranks                                       |
| `clusterKeys`          | string\[] | Cluster keys (format `v<N>-c<N>`)                           |

All fields are optional. An empty cohort `{}` includes all projects.

### POST /colosseum\_copilot/analyze

Summarize tag/track distributions for a cohort.

```bash theme={null}
curl -X POST "$COLOSSEUM_COPILOT_API_BASE/analyze" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "cohort": { "hackathons": ["breakout", "radar"], "winnersOnly": true },
    "dimensions": ["tracks", "problemTags"],
    "topK": 5,
    "samplePerBucket": 1
  }'
```

**Request parameters:**

| Param             | Type      | Default | Description                                                                                                          |
| ----------------- | --------- | ------- | -------------------------------------------------------------------------------------------------------------------- |
| `cohort`          | object    | -       | Cohort definition (see above), **required**                                                                          |
| `dimensions`      | string\[] | -       | Dimensions to analyze: `tracks`, `problemTags`, `solutionTags`, `primitives`, `techStack`, `targetUsers`, `clusters` |
| `topK`            | int       | 10      | Max buckets per dimension (1–20)                                                                                     |
| `samplePerBucket` | int       | 2       | Sample project slugs per bucket (0–5)                                                                                |

**Response:**

| Field     | Type   | Description                                                                                    |
| --------- | ------ | ---------------------------------------------------------------------------------------------- |
| `totals`  | object | `{ projects, winners }` (counts for the cohort)                                                |
| `buckets` | object | Keyed by dimension name, each an array of `{ key, label, count, share, sampleProjectSlugs[] }` |

***

### POST /colosseum\_copilot/compare

Compare two cohorts across the same dimensions.

```bash theme={null}
curl -X POST "$COLOSSEUM_COPILOT_API_BASE/compare" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "cohortA": { "hackathons": ["breakout"], "winnersOnly": true },
    "cohortB": { "hackathons": ["breakout"], "winnersOnly": false },
    "dimensions": ["tracks", "problemTags"],
    "topK": 5
  }'
```

**Request parameters:**

| Param        | Type      | Default | Description                                                                                                          |
| ------------ | --------- | ------- | -------------------------------------------------------------------------------------------------------------------- |
| `cohortA`    | object    | -       | First cohort definition (see above), **required**                                                                    |
| `cohortB`    | object    | -       | Second cohort definition (see above), **required**                                                                   |
| `dimensions` | string\[] | -       | Dimensions to compare: `tracks`, `problemTags`, `solutionTags`, `primitives`, `techStack`, `targetUsers`, `clusters` |
| `topK`       | int       | 10      | Max items per dimension (1–20)                                                                                       |

**Response:**

| Field     | Type   | Description                                                |
| --------- | ------ | ---------------------------------------------------------- |
| `totalsA` | object | `{ projects, winners }` (counts for cohort A)              |
| `totalsB` | object | `{ projects, winners }` (counts for cohort B)              |
| `results` | object | Keyed by dimension name, each an array of comparison items |

**Comparison item shape:**

| Field       | Type      | Description                           |
| ----------- | --------- | ------------------------------------- |
| `key`       | string    | Dimension value key                   |
| `label`     | string    | Human-readable label                  |
| `countA`    | int       | Count in cohort A                     |
| `shareA`    | number    | Share in cohort A (0–1)               |
| `countB`    | int       | Count in cohort B                     |
| `shareB`    | number    | Share in cohort B (0–1)               |
| `lift`      | number    | Relative difference (shareA / shareB) |
| `delta`     | number    | Absolute difference (shareA − shareB) |
| `examplesA` | string\[] | Sample project slugs from cohort A    |
| `examplesB` | string\[] | Sample project slugs from cohort B    |

***

### GET /colosseum\_copilot/clusters/:key

Fetch cluster details.

```bash theme={null}
curl "$COLOSSEUM_COPILOT_API_BASE/clusters/v1-c12" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT"
```

**Response:**

| Field                    | Type      | Description                                                                                    |
| ------------------------ | --------- | ---------------------------------------------------------------------------------------------- |
| `key`                    | string    | Cluster key (format `v<N>-c<N>`)                                                               |
| `label`                  | string    | Cluster label                                                                                  |
| `summary`                | string    | LLM-generated cluster description                                                              |
| `projectCount`           | int       | Total projects in cluster                                                                      |
| `winnerCount`            | int       | Prize-winning projects in cluster                                                              |
| `representativeProjects` | object\[] | `[{ slug, name, oneLiner, isWinner }]`                                                         |
| `topTags`                | object    | `{ problemTags: [{ tag, count }], primitives: [{ tag, count }], techStack: [{ tag, count }] }` |

***

### POST /colosseum\_copilot/source-suggestions

Suggest a new source for the archive corpus.

```bash theme={null}
curl -X POST "$COLOSSEUM_COPILOT_API_BASE/source-suggestions" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/solana-mev-research",
    "name": "MEV Research Blog",
    "reason": "Great technical analysis of Solana MEV strategies"
  }'
```

**Parameters:**

| Param    | Type   | Required | Description                                        |
| -------- | ------ | -------- | -------------------------------------------------- |
| `url`    | string | Yes      | URL of the source to suggest (must be a valid URL) |
| `name`   | string | No       | Name or title of the source (max 200 chars)        |
| `reason` | string | No       | Why this source would be valuable (max 500 chars)  |

**Response:** `201 Created`

```json theme={null}
{ "message": "Thanks! We'll review your suggestion." }
```

Every submission is reviewed by the team. Approved sources are added to the archive pipeline.

***

### POST /colosseum\_copilot/feedback

Report errors, quality issues, or suggestions to help improve Copilot.

```bash theme={null}
curl -X POST "$COLOSSEUM_COPILOT_API_BASE/feedback" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "category": "quality",
    "message": "Search returned low-relevance results for DePIN query",
    "severity": "medium",
    "context": { "query": "DePIN infrastructure", "endpoint": "/search/projects" }
  }'
```

**Parameters:**

| Param      | Type   | Required | Description                                                          |
| ---------- | ------ | -------- | -------------------------------------------------------------------- |
| `category` | string | Yes      | One of: `error`, `quality`, `suggestion`, `other`                    |
| `message`  | string | Yes      | Description of the issue (max 5000 chars)                            |
| `severity` | string | No       | One of: `low`, `medium` (default), `high`, `critical`                |
| `context`  | object | No       | Structured context such as query, endpoint, error details (max 10KB) |

**Response:** `201 Created`

```json theme={null}
{ "message": "Feedback received. Thank you." }
```

High and critical severity feedback is escalated to the team immediately.

***

## Error handling

All errors return:

```json theme={null}
{ "error": "<message>", "code": "<ERROR_CODE>", "retryable": <boolean> }
```

Server errors (5xx) also include a `requestId` field for log correlation when reporting issues.

| Status | Code                     | Retryable | Meaning                                 |
| ------ | ------------------------ | --------- | --------------------------------------- |
| 400    | `INVALID_JSON`           | No        | Request body contains invalid JSON      |
| 400    | `INVALID_QUERY`          | No        | Bad params or unknown fields            |
| 400    | `BAD_REQUEST`            | No        | Malformed request body                  |
| 401    | `UNAUTHORIZED`           | No        | Missing or invalid PAT                  |
| 403    | `FORBIDDEN`              | No        | Access denied for this resource         |
| 404    | `NOT_FOUND`              | No        | Resource not found                      |
| 413    | `PAYLOAD_TOO_LARGE`      | No        | Request body exceeds 1 MB size limit    |
| 415    | `UNSUPPORTED_MEDIA_TYPE` | No        | Unsupported content encoding or charset |
| 429    | `RATE_LIMITED`           | Yes       | Rate or concurrency limit exceeded      |
| 500    | `INTERNAL_ERROR`         | Yes       | Unexpected server error                 |
| 503    | `SERVICE_UNAVAILABLE`    | Yes       | Infrastructure temporarily unavailable  |

Some 5xx responses may use a more specific `code` derived from the server-side error class instead of `INTERNAL_ERROR`. Treat any 5xx with `retryable: true` as transient and include the `requestId` when reporting issues.

For `429`: check the `Retry-After` header for seconds to wait.


# Archive Corpus
Source: https://docs.colosseum.com/copilot/archive-corpus

All 65+ curated sources in the Copilot archive: cypherpunk heritage, Solana docs, investor research, and more

Copilot's archive is a curated collection of 65+ sources spanning cypherpunk history, Solana protocol documentation, investor research, founder essays, and security analysis. Each source was selected for signal density and relevance to crypto startup research.

The corpus contains 84,000+ indexed documents. Archive search auto-cascades through three retrieval tiers (vector similarity → chunk text search → document text search) to maximize recall.

***

## Cypherpunk Heritage

Foundational cryptography, privacy, and digital currency literature.

| Source                                           | Description                                                       |
| ------------------------------------------------ | ----------------------------------------------------------------- |
| Cryptography Mailing List (metzdowd.com)         | Full pipermail archive, where Bitcoin was first announced         |
| Satoshi Nakamoto Forum Posts                     | Satoshi's original BitcoinTalk forum posts                        |
| Satoshi Nakamoto Emails (Nakamoto Archive)       | Satoshi's emails on cryptography, bitcoin, and P2P research lists |
| Nick Szabo's Essays (Satoshi Nakamoto Institute) | Smart contracts, bit gold, digital bearer instruments             |
| Nick Szabo's Blog (unenumerated)                 | Long-form essays on money, law, and computation                   |
| Nick Szabo's Legacy Essays (szabo.best.vwh.net)  | Early essays on digital cash and secure property                  |
| Robin Hanson: Overcoming Bias (Substack)         | Prediction markets, futarchy, decision theory                     |
| Nakamoto Institute Library (Curated)             | Curated collection of foundational crypto texts                   |
| arXiv Cryptography + Crypto-econ                 | Academic papers on cryptography and crypto-economics              |

***

## Solana Core

Official protocol documentation, governance, and community discussions.

| Source                                       | Description                                 |
| -------------------------------------------- | ------------------------------------------- |
| Solana Improvement Documents (SIMD) Repo     | Formal protocol improvement proposals       |
| SIMD GitHub Discussions                      | Community discussion on SIMDs               |
| SIMD Repo Issues                             | Issue tracker for protocol proposals        |
| Solana Developer Forum (all categories)      | Developer Q\&A and technical discussions    |
| Solana Foundation Core Community Call Notes  | Meeting notes from core community calls     |
| Solana Core Community Call Transcripts       | Full transcripts of community calls         |
| Solana Foundation Delegation Program         | Validator delegation program documentation  |
| Solana Docs (solana.com/docs)                | Official Solana documentation               |
| Agave Validator Docs (docs.anza.xyz)         | Anza's Agave validator client documentation |
| Solana Program Library Docs (spl.solana.com) | SPL token and program library docs          |
| Solana Core Repo Issues + PRs                | Core repository issues and pull requests    |
| Solana Program Library Issues + PRs          | SPL repository issues and pull requests     |
| Agave (Anza) Repo Issues + PRs               | Agave validator repository activity         |
| Solana Stack Exchange Q\&A                   | Community Q\&A on Solana development        |
| Solana Cookbook (Developer Patterns)         | Practical developer patterns and recipes    |
| Solana Official News                         | Official Solana Foundation announcements    |

***

## Breakpoint Conference Transcripts

Talk transcripts from Solana's annual developer conference.

| Source                                  | Year                                                |
| --------------------------------------- | --------------------------------------------------- |
| Solana Breakpoint 2022 Talk Transcripts | 2022                                                |
| Solana Breakpoint 2023 Talk Transcripts | 2023 (Main Stage, Developer Stage, Innovator Stage) |
| Solana Breakpoint 2024 Talk Transcripts | 2024                                                |
| Solana Breakpoint 2025 Talk Transcripts | 2025                                                |

***

## Protocol Documentation

Documentation for major Solana DeFi and infrastructure protocols.

| Source                 | Category                     |
| ---------------------- | ---------------------------- |
| Jupiter Documentation  | DEX aggregator               |
| Orca Documentation     | AMM / concentrated liquidity |
| Raydium Documentation  | AMM / liquidity              |
| Drift Documentation    | Perpetual futures            |
| Meteora Documentation  | Dynamic vaults / liquidity   |
| Marinade Documentation | Liquid staking               |
| Tensor Documentation   | NFT marketplace              |
| Jito Documentation     | MEV / liquid staking         |
| Phantom Documentation  | Wallet                       |

***

## Infrastructure & Tooling

Developer infrastructure, security, and gaming/governance platforms.

| Source                                    | Focus                                       |
| ----------------------------------------- | ------------------------------------------- |
| Helius Blog (RPC/Infra)                   | RPC infrastructure, DAS, webhooks           |
| Helius RPC / Data Docs                    | API documentation                           |
| Jito Research (MEV/Staking)               | MEV research and staking mechanics          |
| Firedancer Docs (Validator Client)        | Jump's high-performance validator client    |
| Triton Docs (Yellowstone, Solana, APIs)   | Real-time data streaming                    |
| Yellowstone gRPC Repo Docs                | gRPC interface for Geyser                   |
| MagicBlock Gaming / Ephemeral Rollup Docs | Fully on-chain gaming infrastructure        |
| MagicBlock Engineering Blog               | Engineering deep dives on ephemeral rollups |
| Squads Governance & Dev Docs              | Multisig and governance tooling             |
| Squads Treasury & Governance Blog         | Treasury management insights                |
| Realms DAO Governance Documentation       | DAO governance tooling                      |

***

## Security Research

Audit firms and security researchers covering Solana.

| Source                       | Focus                                      |
| ---------------------------- | ------------------------------------------ |
| Sec3 Security Blog & Reports | Solana program security analysis           |
| OtterSec Blog                | Security audits and vulnerability research |
| Neodyme Blog                 | Exploit analysis and security research     |

***

## Investor Research

Crypto-native venture research and market analysis.

| Source                      | Focus                                                     |
| --------------------------- | --------------------------------------------------------- |
| Paradigm Research           | Protocol design, mechanism design, DeFi research          |
| a16z Crypto                 | Market structure, regulatory analysis, builder frameworks |
| Multicoin Capital           | Crypto investment theses, market analysis                 |
| Pantera Capital             | Macro crypto research                                     |
| Alliance DAO Essays         | Builder ecosystem, accelerator insights                   |
| Placeholder VC              | Token economics, network effects                          |
| Electric Capital            | Developer ecosystem data and reports                      |
| Galaxy Research             | Market analysis, DeFi landscape, institutional research   |
| Coin Metrics Research       | On-chain data analysis and market metrics                 |
| Chainalysis Blog & Research | Blockchain analytics, compliance, market trends           |

***

## Founder & Builder Essays

Essays on startups, technology, and building companies.

| Source                     | Author/Org                                      |
| -------------------------- | ----------------------------------------------- |
| Paul Graham Essays         | Y Combinator founder. Startups, taste, building |
| Sam Altman Blog            | AI, startups, technology                        |
| Colosseum Blog & Podcast   | Hackathon insights, builder stories, ecosystem  |
| Superteam Blog (Ecosystem) | Solana ecosystem analysis and builder resources |

***

## The Grid: Crypto Ecosystem Metadata

In addition to the archive corpus, Copilot queries [The Grid](https://thegrid.id/) for crypto ecosystem metadata.

| Metric                  | Value                                          |
| ----------------------- | ---------------------------------------------- |
| Products tracked        | 6,300+ (all ecosystems)                        |
| Data points per product | Type, status, on-chain metadata, support graph |

The Grid provides saturation counts (how many products exist in a given category), product type classification, and competitive landscape data. When Copilot reports a "crowdedness score" or checks for incumbents, it's querying The Grid.

***

## Source freshness and suggestions

Sources refresh on varying intervals. Protocol docs update within days, historical archives are static, and Breakpoint transcripts are added after each conference. The corpus grows over time.

To suggest a source, tell your agent: *"Suggest adding \[URL] to the Copilot archive."* It calls `POST /source-suggestions` and our team reviews every submission.


# Authentication
Source: https://docs.colosseum.com/copilot/authentication

How to authenticate with the Copilot API using Personal Access Tokens

Copilot uses Personal Access Tokens (PATs) for authentication. Every API request requires a valid token.

## Getting a Token

<Steps>
  <Step title="Sign in to Colosseum Arena">
    Go to [colosseum.com/arena](https://colosseum.com/arena) and sign in with your account. If you don't have one, sign up first. Any auth method works (email, Google, GitHub).
  </Step>

  <Step title="Open the Copilot setup page">
    Navigate to [colosseum.com/arena/copilot](https://colosseum.com/arena/copilot). If you're not signed in, you'll be redirected to the sign-up page.
  </Step>

  <Step title="Generate and copy your token">
    Click **Generate your token**. The token appears once — copy it immediately using the **Copy** button. The full token is only shown on this page.

    Below the token, you'll see a ready-to-paste `export` snippet for your terminal. Copy that too.
  </Step>

  <Step title="Store it securely">
    Add the token to your shell profile so it persists across sessions:

    ```bash theme={null}
    # Add to ~/.zshrc, ~/.bashrc, or equivalent
    export COLOSSEUM_COPILOT_API_BASE="https://copilot.colosseum.com/api/v1"
    export COLOSSEUM_COPILOT_PAT="eyJhbGciOi..."
    ```

    Then reload your shell: `source ~/.zshrc`
  </Step>
</Steps>

## Using Your Token

Pass the token as a Bearer token in the `Authorization` header:

```bash theme={null}
curl -X POST "$COLOSSEUM_COPILOT_API_BASE/search/projects" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT" \
  -H "Content-Type: application/json" \
  -d '{"query": "MEV protection on Solana"}'
```

If you're using the Copilot skill (Claude Code, Codex, or OpenClaw), the skill reads `COLOSSEUM_COPILOT_PAT` automatically. You don't need to set the header manually.

<Tip>
  Test your token with a quick `curl` before configuring your coding assistant:

  ```bash theme={null}
  curl "$COLOSSEUM_COPILOT_API_BASE/filters" \
    -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT"
  ```

  A successful response returns a JSON object with available filters (tracks, hackathons, clusters, etc.).
</Tip>

## Regenerating Your Token

Tokens expire after 90 days. You can also regenerate early if needed:

1. Go to [colosseum.com/arena/copilot](https://colosseum.com/arena/copilot)
2. Click **Regenerate token**
3. Confirm in the dialog. This **invalidates your current token immediately**
4. Copy the new token and update your environment variables

After regenerating, any tool or script using the old token will receive `401` errors until you update it. If you suspect a token has been compromised, regenerate immediately.

See [API Reference](/copilot/api-reference#rate-limits) for rate limits and [API Reference](/copilot/api-reference#error-handling) for error codes.


# Capabilities
Source: https://docs.colosseum.com/copilot/capabilities

What you can do with Colosseum Copilot: use cases, modes of operation, and quality guarantees

Copilot is designed for founders researching startup opportunities in the Solana ecosystem. It answers questions conversationally by default, and runs a full 8-step research workflow when you explicitly opt in.

## Use cases

<Columns>
  <Card icon="lightbulb" href="/copilot/examples/b2b-stablecoin-payments" title="Validate a startup idea">
    Search the builder corpus and accelerator portfolio, flag who's already working on it, classify the gap, and find where differentiation exists.
  </Card>

  <Card icon="magnifying-glass" href="/copilot/examples/ai-agent-payments" title="Find who's building this">
    Surface relevant hackathon projects, accelerator companies, and products across crypto, with honest crowdedness scores.
  </Card>

  <Card icon="arrows-rotate" href="/copilot/examples/consumer-apps" title="Translate your background">
    Map your skills to underserved Solana verticals, surface relevant projects, and frame opportunities around what you already know.
  </Card>

  <Card icon="scale-balanced" href="/copilot/examples/mev-batch-auctions" title="Challenge a thesis">
    Test a claim, bullish or bearish, against real project and archive data. No sycophancy, no dismissal, just evidence.
  </Card>

  <Card icon="scroll" href="/copilot/examples/privacy-stablecoin" title="Research concepts">
    Trace how ideas evolved from cypherpunk mailing lists and Satoshi's writings through research papers to live implementations.
  </Card>

  <Card icon="chart-column" href="/copilot/examples/compare-gaming-tracks" title="Compare hackathons">
    Contrast submission volume, quality trends, and category shifts across hackathons, tracks, or time periods.
  </Card>
</Columns>

See [Examples](/copilot/examples) for full prompt/response pairs from real evaluation runs.

## Modes of operation

### Conversational (default)

Answers questions with targeted API calls. Cites sources inline: project names, archive titles, URLs. Keeps responses concise. Offers to go deeper when the topic warrants it.

**Evidence floors by query type:**

| Query type        | Required evidence                                                  |
| ----------------- | ------------------------------------------------------------------ |
| Pure retrieval    | Builder project evidence (project slugs)                           |
| Archive retrieval | Archive evidence (document titles)                                 |
| Comparison        | Project evidence for each side + archive citation                  |
| Evaluative        | Project evidence + archive citation + landscape evidence           |
| Build guidance    | Project evidence + archive citation + incumbent/landscape evidence |

### Deep Dive (explicit opt-in)

Full 8-step research workflow. Activates when you say:

* "vet this idea"
* "deep dive" / "full analysis"
* "should I build X?" / "is X worth building?"
* Accept the offer: "Want me to do a full deep-dive on this?"

**The 8 steps:**

1. **Parallel data gathering**: simultaneous searches across projects, archives, and web
2. **Project search**: semantic search with filters (hackathon, track, tech stack, winners, accelerator)
3. **Archive search**: vector + text search across 65+ curated sources with auto-cascade
4. **Landscape check**: The Grid product data + web search for current incumbents
5. **Hackathon analysis**: tag distributions, track trends, cluster groupings
6. **Incumbent validation**: honest assessment with gap classification (full / partial / false)
7. **Opportunity ranking**: identify the strongest wedge based on evidence
8. **Structured report**: similar projects, archive insights, landscape, opportunities, deep dive on top opportunity (incumbent analysis, revenue model, GTM, risks)

**Report output includes:**

* 5–8 similar projects with slugs and context
* 3–5 archive insights grounded in foundational concepts
* Current landscape per research angle
* Key patterns, gaps, and trends
* Deep dive: incumbent analysis, problem statement, revenue model, GTM strategy, founder-market fit, why crypto/Solana, risks


# Examples
Source: https://docs.colosseum.com/copilot/examples

Real prompt/response pairs from Copilot evaluation runs across 12 scoring dimensions

These are real prompt/response pairs from Copilot's evaluation suite, selected from runs that demonstrated strong performance across all 12 evaluation dimensions: workflow compliance, source grounding, incumbent honesty, business plausibility, data quality, report structure, specificity, foundational concept integration, attribution quality, source balance, actionability, and freshness.

Click any example to see the full unedited Copilot output.

***

## [Consumer Apps for Mobile Developers](/copilot/examples/consumer-apps)

<Badge>Generated with Sonnet 4.6</Badge> · [Translate your background](/copilot/capabilities#use-cases)

> I'm a mobile developer — shipped a few apps on the App Store with 50k+ downloads. Never touched crypto before but I keep hearing about Solana being fast and cheap. What kinds of consumer apps are people building? I want something normies would actually use, not another dashboard for degens.

Copilot mapped the user's mobile dev background directly to underserved verticals, surfacing Trepa (C3, React Native prediction app) and Cron (native iOS P2P payments) as proof points. It identified that native iOS is structurally underrepresented (React dominates at 41% of submissions) and recommended a live game show app with USDC prizes — solving HQ Trivia's fatal unit economics problem (\$500 in PayPal fees per 10K prizes vs \$0.10 on Solana).

***

## [B2B Stablecoin Payments](/copilot/examples/b2b-stablecoin-payments)

<Badge>Generated with Sonnet 4.6</Badge> · [Validate a startup idea](/copilot/capabilities#use-cases)

> I work in logistics and supply chain at a Fortune 500. We spend millions on cross-border payment fees and settlement takes 3-5 days. I've been researching stablecoins and think there's a massive opportunity to cut out SWIFT entirely for B2B trade finance. Is anyone doing this on Solana? What would a realistic MVP look like?

Copilot immediately surfaced CargoBill (C3 accelerator, 1st Place Stablecoins) as the most direct predecessor, then classified the gap as "Partial — Segment": CargoBill targets freight forwarders and logistics operators, not the Fortune 500 buyers who generate the payment flows. It identified OpenFX (\$23M Accel, \$10B annualized volume) and Fin (\$17M) as the funded competitive threats, and recommended an ERP-integrated stablecoin treasury module targeting the corporate AP side of the same transaction.

***

## [Gaming Track: Radar vs. Renaissance](/copilot/examples/compare-gaming-tracks)

<Badge>Generated with Sonnet 4.6</Badge> · [Compare hackathons](/copilot/capabilities#use-cases)

> Compare gaming track submissions between Radar and Renaissance.

Copilot pulled submission counts, prize winners, and project details for both hackathons' gaming tracks, then surfaced the key thematic shift: Radar's top prizes went to DeFi/trading game hybrids (The Arena, Windfall, TrenchTown), while Renaissance rewarded DePIN-gaming crossovers (MeshMap + City Champ) and infrastructure-layer thinking (Honeycomb). It identified the sophistication shift from wallet integration and NFT ownership toward ZK/VDF fairness, ephemeral rollups, and cross-track DePIN plays.

***

## [MEV Batch Auctions](/copilot/examples/mev-batch-auctions)

<Badge>Generated with Sonnet 4.6</Badge> · [Challenge a thesis](/copilot/capabilities#use-cases)

> My thesis is that Solana doesn't need another DEX — it needs better execution infrastructure. I want to build a batch auction system that eliminates MEV for retail traders. Think CowSwap but native to Solana's architecture. Has anyone tried this?

Copilot surfaced three accelerator companies already building MEV-protective DEXs on Solana: Archer Exchange (C4, DFBA batch auctions), URANI (C1, intent-based aggregator), and DARKLAKE (C2, ZK-proof matching). Rather than validating the DEX angle, it identified the real gap: no one has built the infrastructure layer — a batch-settlement routing layer beneath Jupiter that existing DEXs route through. Cited \$370-500M extracted from Solana users in 16 months as the TAM proxy.

***

## [AI Agent Payments](/copilot/examples/ai-agent-payments)

<Badge>Generated with Sonnet 4.6</Badge> · [Find who's building this](/copilot/capabilities#use-cases)

> Everyone's talking about AI agents but nobody's figured out payments. I want to build a protocol where AI agents can pay for services programmatically — like a Stripe for autonomous agents. Has anyone in the Solana ecosystem tried this? What's the architecture look like?

Copilot identified a dense cluster (crowdedness 325) and surfaced MCPay (C4 accelerator, 1st Place Stablecoins) as the most validated project — MCP tool monetization via x402. It cited Nick Szabo's micropayments essay (machines have no mental accounting barrier) and a16z's "Tourists in the Bazaar" framing to argue the real gap isn't payment plumbing (x402 is winning) but agent spending policy engines — the "Brex for AI Agents" layer that manages budgets, credit lines, and compliance.

***

## [Privacy-Preserving Stablecoin](/copilot/examples/privacy-stablecoin)

<Badge>Generated with Sonnet 4.6</Badge> · [Research concepts](/copilot/capabilities#use-cases)

> I want to build a privacy-preserving stablecoin — like a Zcash-style shielded pool but for USDC on Solana. Users deposit USDC, get a private balance, and can transfer without anyone seeing amounts or recipients. I know Tornado Cash got sanctioned but I think there's a compliant way to do this with selective disclosure and ZK proofs. What does the landscape look like and is this even possible on Solana technically?

Copilot identified a critical Token-2022 limitation: Confidential Balances hide transfer amounts but NOT sender/recipient addresses — a full Zcash-style shielded pool requires a separate program. It surfaced Umbra (\$155M ICO commitments, Feb 2026 launch) as the closest competitor using MPC, then traced the compliance-first approach through a16z's 2022 paper on privacy-protecting regulatory solutions. The recommended wedge: regulated B2B private payments (payroll, supplier payments) where institutions can't use public chains.

***

## Evaluation dimensions

Each example was scored across these 12 dimensions:

| Dimension                        | What it measures                                            |
| -------------------------------- | ----------------------------------------------------------- |
| Workflow compliance              | Did it follow the research workflow correctly?              |
| Source grounding                 | Is every claim traced to a specific source?                 |
| Incumbent validation honesty     | Does it honestly flag competitors and saturation?           |
| Business plausibility            | Is the revenue model and GTM realistic?                     |
| Data quality feedback            | Are the cited sources relevant and high-quality?            |
| Report structure compliance      | Does the output follow the required format?                 |
| Specificity score                | Are claims backed by concrete numbers?                      |
| Foundational concept integration | Do archive sources inform the thesis?                       |
| Attribution quality              | Does every claim map to a specific source?                  |
| Source balance                   | Is there a healthy mix of projects, archives, and web data? |
| Actionability                    | Can a founder act on this report?                           |
| Freshness                        | Is the data current (within 6 months)?                      |


# AI Agent Payments
Source: https://docs.colosseum.com/copilot/examples/ai-agent-payments

Example: Exploring AI agent payment infrastructure on Solana

<Badge>Generated with Sonnet 4.6</Badge> · [Find who's building this](/copilot/capabilities#use-cases)

> Everyone's talking about AI agents but nobody's figured out payments. I want to build a protocol where AI agents can pay for services programmatically — like a Stripe for autonomous agents. Has anyone in the Solana ecosystem tried this? What's the architecture look like?

***

<Info>
  **What follows is Copilot's unedited deep-dive output** — the full research report generated from the prompt above.
</Info>

## 1. Similar Projects (What's Already Been Built)

The Colosseum ecosystem has a surprisingly dense cluster (v1-c14: "Solana AI Agent Infrastructure", crowdedness 325) around this exact thesis. The space is active — not empty — but no single project has locked in the "Stripe" position.

> **Note:** These are hackathon submissions — demos and prototypes, not production products. Many may no longer be active. They're included as inspiration and to show what's been tried before, not as a competitive landscape.

**Prize winners / accelerator-backed (highest signal):**

* **MCPay** (`mcpay`) — Cypherpunk 1st Place Stablecoins + **C4 Accelerator**. "Charge for Model Context Protocol tools, data sources, and specialized agent capabilities using x402." The most validated project in this cluster: MCP tool monetization via x402 on Solana, single-person team (@microchipgnu).
* **Latinum Agentic Commerce** (`latinum-agentic-commerce`) — Breakout 1st Place AI (\$25K). Payment middleware + MCP-compatible wallet. "Developers have created thousands of MCP servers, but there has been no way to monetize them." Live at latinum.ai.
* **Corbits.dev** (`corbits.dev`) — Cypherpunk 2nd Place Infrastructure (\$20K). x402-based API payment proxy: "no accounts, no keys, just pay and go." Built an open-source merchant RevOps dashboard.

**Non-winners with noteworthy architecture:**

* **Agent-Cred** (`agent-cred`) — Hotkey/coldkey dual-key architecture (borrowed from Bittensor) for secure autonomous spending.
* **AI Economy Protocol (AEP)** (`ai-economy-protocol-(aep)`) — Full stack: service discovery → price negotiation → escrow → automated settlement.
* **SolSynapse** (`solsynapse`) — Decentralized agent communication + intent-based escrow + settlement.
* **Zen7 Labs** (`zen7-labs`) — DePA (Decentralized Payment Agent) framework: non-custodial agent wallets, autonomous budget allocation, cross-chain.
* **Tedix** (`tedix-ai-commerce-powered-by-solana`) — AI commerce via MCP + x402, targeting purchase of real-world goods directly in AI chat.
* **Electrodo Pay** (`electrodo-pay`) — Breakout AI track. Web3 payment engine specifically for industrial/ESG AI agents.

***

## 2. Archive Insights

**The "x402" standard is the pivot point everyone's converging on:**

* **Galaxy Research, "Agentic Payments and Crypto's Emerging Role in the AI Economy"** (Jan 2026) — Coinbase launched x402 in May 2025 — an HTTP 402 "Payment Required" revival. Galaxy calls this family "Agentic Payment Standards (APS)" and frames them as giving "agents access to the internet's full economic surface area." Key insight: "x402 is built for software paying other software."
* **a16z, "Tourists in the Bazaar"** (Sam Broner, Feb 2026) — The most strategically important framing. "Agents will behave like locals, not tourists." Dominant agents will consolidate into business-like platforms needing **B2B payment terms, working capital, and credit** — not per-transaction micropayments. This is the Stripe-vs-Amex distinction applied to agents.
* **a16z, "AI needs crypto — especially now"** (Feb 2026) — Without blockchain-based identity, "agent experiences are fragmented and onerous to load in context." Public keys as agent identifiers unlock reputation, blocklists, slashing.
* **Galaxy Research, "Raising for Robots"** (Feb 2026) — "Agents need a natively digital medium of exchange that can operate continuously, globally, and without human intervention. Stablecoins give agents a programmable, dollar-denominated medium of exchange that doesn't require bank accounts."
* **Superteam, "Return of the L1 Wars: It's All About AI Agents"** (Sep 2025) — The infrastructure requirement is explicit — "millisecond feedback loops syncing with LLM time-to-first-token rates." PINs, OTPs, 2FA are human-designed and break autonomous agent flows.
* **Nick Szabo, "The Mental Accounting Barrier to Micropayments"** (Nakamoto Institute) — Classic essay arguing micropayments fail for humans because of cognitive overhead. The insight that inverts for agents: **machines have no mental accounting barrier.**

***

## 3. Current Landscape

**x402 is winning as the base protocol layer:**

* Coinbase launched x402 May 2025; Solana Foundation published official integration guides.
* Multiple Cypherpunk hackathon projects (MCPay, Corbits, Tedix) independently converged on x402 as the plumbing.
* Pantera Capital newsletter (Nov 2025) confirmed x402 as "universal standard for AI-driven payments."

**The architectural stack being assembled:**

* **Layer 1 (Protocol):** x402 HTTP standard — pay per request, no API keys
* **Layer 2 (Wallet/Identity):** Hotkey/coldkey architecture or MCP wallet middleware — budget allocation per agent
* **Layer 3 (Settlement):** Solana + USDC stablecoins — sub-second finality, \~\$0.001 fees
* **Layer 4 (Agent Economy):** Service discovery, negotiation, A2A escrow

**What's NOT yet built:**

* No project has built **credit rails** for agents (the "Amex corporate card" layer a16z points to)
* No project has built **spending policy engines** (per-category limits, anomaly detection, compliance rules)
* **Merchant-side tooling** is thin — Corbits has a dashboard but no SDK, webhooks, or fraud layer
* **Cross-agent routing** — when Agent A hires Agent B who hires Agent C, the payment chain is unresolved

***

## 4. Key Insights

* **The "kill the API key" framing is sticky and right.** Every prize-winning project independently landed on this insight. Subscriptions + API keys are the wrong model when the consumer is autonomous software.
* **MCP created the distribution moment.** Thousands of MCP servers built in months — massive supply of un-monetized compute that needs a payment layer.
* **x402 is standardization, not lock-in.** The Stripe position is not "own x402," it's "own the best developer experience on top of x402."
* **Stablecoins + Solana = unique fit.** Solana's throughput (65K TPS, \~400ms finality) with stablecoin settlement eliminates the two objections to crypto payments (volatility, speed).
* **Convergent finding: Security model for agent wallets is unsolved.** Agent-Cred's hotkey/coldkey architecture addresses this directly; Latinum and MCPay leave it to the developer.

***

## 5. Opportunities and Gaps

* **The "Stripe" gap is really the "Brex/corporate card" gap.** Individual micropayment routing is being solved (x402). The unsolved problem is managing *aggregate* agent spending: budgets, credit lines, approval policies, spend analytics, invoicing.
* **Spending policy engine / risk layer.** When an agent can spend autonomously, who sets the rules? Per-vendor limits, per-category caps, time-bounded budgets, anomaly detection. Nobody's built it.
* **Agent identity → creditworthiness.** An agent with on-chain transaction history, on-time payment record, and verifiable reputation can negotiate net-30 terms with API providers. Building the credit scoring model for agents is a unique opportunity.
* **Web2 bridge.** Most agents also need to pay Web2 services that don't speak x402. A bridge layer between USDC on Solana and Web2 payment rails is a gap.
* **A2A settlement routing.** When orchestrator agents hire sub-agents, who handles the payment graph? Payment propagation, partial refunds, and escrow release conditions across multi-agent pipelines are unsolved.

***

## 6. Deep Dive: Top Opportunity — The "Brex for AI Agents" Layer

### The Problem

x402 solves the *plumbing* — an agent can pay an API. What it doesn't solve: **who manages the agent's money.** The gap: an autonomous agent with unrestricted wallet access is either (a) too locked down to be useful, or (b) a liability. Programmable spending policies with on-chain enforcement are completely absent.

### Market Landscape (As of 2026-03-06)

* MCPay and Latinum are the closest, but both delegate budget management to developers (hardcoded limits in code). Neither provides a policy engine, a dashboard, or a credit facility.
* No accelerator-backed project targets the enterprise segment (companies running fleets of agents with audit requirements).
* Web2 corporate card analogs (Brex, Ramp) have no crypto equivalent for agent-operated wallets.

### Revenue Model

* **SaaS tier:** Flat fee per agent wallet deployed
* **Take rate:** 0.1-0.3% on transactions routed through the policy engine
* **Credit facility:** Interest on working capital lines extended to high-reputation agents
* **Enterprise:** Custom compliance/audit packages for companies running agent fleets

### Go-to-Market

* Start with MCP server operators already getting paid via MCPay/Latinum but with no spend controls — position as the "treasury layer"
* Developer-led: open-source the policy engine Rust program, monetize the dashboard + credit layer
* Partnership angle: integrate as the "spending controls" SDK that MCPay and Latinum reference in their docs

### Founder-Market Fit

* Strongest for builders with: (a) prior fintech compliance / corporate card experience, or (b) deep MCP/agent ecosystem credibility
* MCPay won with one person — but the credit/enterprise layer likely needs a BD-capable co-founder

### Why Crypto / Why Solana

* Policy enforcement needs to be trustless — a smart contract spending policy is verifiable and tamper-proof
* Solana's throughput handles thousands of micropayments/second without batching overhead
* USDC settlement means agents, operators, and vendors all settle in dollars — no volatility exposure
* On-chain transaction history is the natural input for agent credit scoring — no credit bureau needed

### Risks

* **Protocol risk:** If Google's A2A or Anthropic's own payment layer wins over x402, the underlying plumbing changes. Mitigate by building protocol-agnostic policy logic.
* **Crowding in the base layer:** MCPay (C4), Latinum (Breakout winner), and Corbits are all credible teams already funded. Going up the stack (policy, credit) is the differentiation.
* **Trust and liability:** Autonomous spending creates real liability exposure. Regulatory clarity on "who is responsible when an agent overspends" is unclear.


# B2B Stablecoin Payments
Source: https://docs.colosseum.com/copilot/examples/b2b-stablecoin-payments

Example: Validating a B2B cross-border stablecoin payments startup idea on Solana

<Badge>Generated with Sonnet 4.6</Badge> · [Validate a startup idea](/copilot/capabilities#use-cases)

> I work in logistics and supply chain at a Fortune 500. We spend millions on cross-border payment fees and settlement takes 3-5 days. I've been researching stablecoins and think there's a massive opportunity to cut out SWIFT entirely for B2B trade finance. Is anyone doing this on Solana? What would a realistic MVP look like?

***

<Info>
  **What follows is Copilot's unedited deep-dive output** — the full research report generated from the prompt above.
</Info>

## Similar Projects

> **Note:** These are hackathon submissions — demos and prototypes, not production products. Many may no longer be active. They're included as inspiration and to show what's been tried before, not as a competitive landscape.

* **CargoBill** (`cargobill`) — 1st Place Stablecoins, Breakout hackathon; **C3 accelerator portfolio**. Stablecoin payments for supply chain logistics via multisig business wallets and enterprise on/off-ramps on Solana. Active at cargobill.co. This is the most direct predecessor — targets freight forwarders and logistics operators, not Fortune 500 treasury/procurement teams.
* **Stablecoins FX** (`stablecoins-fx`) — Smart execution layer for stablecoins enabling auditable FX and treasury operations for institutional users; targets treasury managers and DAOs (Cypherpunk).
* **MISK.FI** (`misk.fi-stablecoin-payments-for-your-business`) — Stablecoin infrastructure for B2B netting, escrow, and verifiable on-chain receipts; positions as a Stripe-equivalent for crypto-native businesses (Cypherpunk).
* **Brace** (`brace`) — B2B stablecoin payment infrastructure with automated treasury management and digital invoicing; targets SMEs and international vendors (Breakout).
* **Trade:see** (`trade:see`) — Automated escrow and settlement platform for SME exporters using USDC + oracle-verified settlement; directly targets logistics companies (Cypherpunk).
* **Credible Finance** (`credible-finance-1`) — 2nd Place Stablecoins, Cypherpunk; **C4 accelerator**. USD-INR stablecoin remittance rail for banks, fintechs, and businesses; offers guaranteed FX rates 2% better than Wise/Remitly.
* **Globachain** (`globachain`) — Compliant B2B cross-border stablecoin payments for African businesses, focusing on emerging market corridors with regulatory compliance built in (Breakout).

***

## Archive Insights

* **Pantera Capital "Escape Velocity"** — Explicitly calls out B2B cross-border as the killer stablecoin use case: "Stablecoins offer a 10x value proposition to traditional payment rails across both B2C payments (e.g., remittances) as well as B2B cross-border transactions." Contextualizes the opportunity as a corridor-by-corridor replacement of SWIFT where dollar demand is highest.
* **Squads Blog "The Stablecoin Era"** — Enterprise PSPs (payment service providers) are already internalizing stablecoin rails; "instantaneous settlement, seamless currency conversions, and cost savings are already being realized in practical applications by enterprises." Positions Solana as the preferred settlement layer given fees and throughput.
* **"Contracts with Bearer" (Nick Szabo, Nakamoto Institute)** — The foundational concept underpinning all of this: digital bearer certificates replace intermediary-heavy settlement with direct P2P transfer where possession equals ownership. Smart contracts on Solana are this primitive realized at scale — the 60-year-old promise of bearer settlement, now programmable.
* **"The Geodesic Market" (Nakamoto Institute)** — Argues that bearer transactions executed, cleared, and settled by cryptographic protocol collapse the cost of financial intermediation to near-zero. The \$30-50 SWIFT wire fee is pure intermediary rent — geodesic settlement captures it.
* **Paradigm Research "Electronification, Trading, and Crypto"** — Draws the historical parallel to the 1960s stock-trading "Paperwork Crisis," which forced electronification of equity settlement. Trade finance is experiencing its equivalent crisis today: paper-based letters of credit, fax confirmations, and 5-10 day processing are structurally identical to the pre-DTCC settlement system. Blockchain is the equivalent forcing function.

***

## Current Landscape

### Angle 1: Enterprise-Grade B2B Stablecoin Settlement (SWIFT Replacement)

* **Key players**: OpenFX (\$23M Accel, achieved \$10B annualized volume in under 12 months, 90% faster/90% cheaper than traditional FX), Fin (\$17M, ex-Citadel, global stablecoin B2B transactions), BVNK (enterprise stablecoin payment infrastructure, UK-based), Ripple (institutional focus with RLUSD), Circle (USDC infrastructure, direct enterprise integrations), Stripe (stablecoin B2B payments product launched 2025)
* **Recent developments**: GENIUS Act (US, 2025) and MiCA (EU) providing regulatory clarity; 90% of financial institutions now using or planning stablecoin integration; B2B stablecoin payment volume surged from under \$100M/month (early 2023) to \$6B+/month (mid-2025); Solana processed \$1T+ in stablecoin volume in 2025; VISA, Stripe, and Worldpay partnerships with Solana for stablecoin settlement
* **Research & standards**: McKinsey estimates true payment-specific stablecoin volume at \$390B in 2025, B2B leading at \$226B (60% of total); US Treasury projects stablecoin market cap reaching \$2T by 2028; Goldman Sachs published "Stablecoin Summer" institutional research
* **Maturity**: Growing — fast-moving, well-funded, with both crypto-native and TradFi incumbents entering

### Angle 2: Programmable Trade Finance on Solana (LoC Tokenization)

* **Key players**: Centrifuge (invoice tokenization via Tinlake protocol, Ethereum), Goldfinch (DeFi loans to emerging market lenders, Ethereum), SC Ventures + SWIAT + Olea (blockchain supplier financing, announced April 2025), Marco Polo Network (trade finance blockchain), RWA.io — all predominantly Ethereum-based; **no dominant Solana-native player**
* **Recent developments**: Standard Chartered enabled supplier financing via blockchain (April 2025); tokenized LCs can process in hours vs 5-10 days physically; blockchain projected to handle \$34.6B in supply chain finance by 2034 (vs \$2.4B today, 39.4% CAGR)
* **Research & standards**: Solana Token-2022 transfer hooks and confidential transfers are purpose-built for compliant trade document workflows; Squads multisig enables multi-party approval mimicking LC confirmation flow
* **Maturity**: Emerging on Solana — real whitespace for a Solana-native trade finance protocol

### Angle 3: Emerging Market Freight Corridors

* **Key players (Solana-native)**: Credible Finance (C4, USD-INR corridor, banks/fintechs as distribution), Tsara (Africa, stablecoin checkout API for B2B marketplaces), Globachain (Africa, compliant cross-border), LocalPay (C3, emerging market consumer wallet), Vikki Cross-Border Remit (Cypherpunk, SME remittance)
* **Recent developments**: 77% of corporates report interest in stablecoin cross-border payments; African and Southeast Asian corridors show highest SWIFT pain (currency volatility + banking access); Credible Finance (C4) offers guaranteed FX rates 2% better than Wise/Remitly for USD-INR specifically
* **Maturity**: Growing but fragmented by corridor — no corridor-agnostic enterprise layer yet on Solana

***

## Key Insights

* **Pattern — SME saturation, Fortune 500 whitespace**: The 202-project "Stablecoin Payment Rails and Infrastructure" cluster is overwhelmingly SME/mid-market focused. Cohort analysis across 2,992 Cypherpunk + Breakout submissions shows "slow cross-border payments" as a problem tag concentrated almost entirely in Cypherpunk submissions — all non-accelerator companies. No Colosseum project explicitly targets Fortune 500 procurement/treasury integration with ERP hooks.
* **Gap — Solana-native programmable trade finance**: Letters of Credit, purchase order financing, and invoice factoring on Solana are absent. All existing blockchain trade finance runs on Ethereum (Centrifuge, Goldfinch). Solana's throughput and Token-2022 extension infrastructure are technically superior for this use case — the gap exists because the founders with the TradFi access haven't built here yet.
* **Trend — Corporate treasury teams are moving**: 60% of Fortune 500 executives report active blockchain initiatives. Amazon, Walmart, Fidelity, and JPMorgan are publicly experimenting. The Fortune 500 treasury is not a "future market" — it's an active adoption curve. The question is which product captures enterprise switching.
* **Trend — OpenFX speed**: \$0 to \$10B annualized volume in under 12 months signals the enterprise market is ready to move fast once a trusted, compliant product exists. The window to establish a Solana-native ERP-integrated alternative is likely 12-24 months before OpenFX/Fin extend coverage and consolidate.

***

## Opportunities & Gaps

* **Underexplored**: Fortune 500 procurement-integrated stablecoin treasury — ERP hooks (SAP/Oracle AP modules), multi-entity netting, configurable approval workflows, SOC2-grade audit logs. CargoBill doesn't serve this; OpenFX/Fin don't offer Solana-native on-chain programmability.
* **Emerging niche**: Programmable trade finance on Solana — tokenized letters of credit and invoice tokenization using Token-2022 and Squads multisig, targeting the \$13.4B supply chain finance market. No incumbent owns this vertical on Solana.
* **Saturated zone**: General B2B stablecoin remittance targeting SMEs and logistics SMEs — CargoBill, Brace, Vikki, Tsara, Globachain all competing here. Do not launch a 203rd product in this cluster without a concrete wedge.

***

## Deep Dive: Top Opportunity

**Fortune 500 ERP-Integrated Stablecoin Treasury Module**

### Incumbent Analysis

> **Direct Competitor Alert:** CargoBill (`cargobill`, Breakout 1st place / C3) is building stablecoin payments for supply chain logistics on Solana. Problem match: high cross-border logistics costs, slow settlement. Target user: freight forwarders and logistics operators. Status: active, accelerator-backed, live product at cargobill.co.
>
> **Why this is a Partial gap — Segment, not a False gap:** CargoBill targets logistics operators and freight forwarders (the carriers and intermediaries), not the Fortune 500 buyers who generate the payment flows. CargoBill is Stripe for the logistics layer; the opportunity is a treasury module for the corporate side of the same transaction — the SAP-connected accounts payable team at a Fortune 500 that originates vendor payments. To differentiate, you must own the enterprise buyer's ERP integration and compliance workflow, not the logistics middleware layer.

* **Who are the incumbents?** For general enterprise cross-border B2B payments: OpenFX (\$23M Accel, \$10B annualized volume, Solana-adjacent), Fin (\$17M ex-Citadel), Ripple (enterprise RLUSD), SWIFT gpi (the incumbent being disrupted). For supply-chain-specific: Kyriba and GTreasury (enterprise treasury management systems with basic FX hedging, no stablecoin settlement). CargoBill is the closest Solana-native competitor but is in a different segment.
* **What do they currently offer?** OpenFX: FX swap infrastructure using stablecoins as intermediary, primarily API-first for fintechs and payment processors, not ERP-integrated. Kyriba: Enterprise treasury platform with FX hedging and cash flow forecasting but SWIFT-only settlement with no on-chain programmability. CargoBill: Multisig USDC payments + on/off-ramps for logistics operators; no SAP/Oracle integration, no multi-entity corporate netting, no compliance audit trail for Fortune 500 procurement.
* **Gap classification**: Partial gap — Segment. The Fortune 500 accounts payable team needs: (1) SAP/Oracle/Coupa plugin for invoice-triggered payment, (2) configurable approval workflows matching existing authorization matrices, (3) multi-entity netting to offset intercompany flows, (4) SOC2 Type II audit trail for finance team compliance, (5) direct bank account reconciliation. None of the existing Solana-native players offer this stack. OpenFX is closest but isn't Solana-native and doesn't offer ERP integration.
* **Evidence**: CargoBill product description shows multisig wallets, cashback, and on/off-ramps — logistics operator features, not corporate treasury features. OpenFX positions itself as infrastructure for fintechs and PSPs, not direct Fortune 500 integration. Kyriba's 2025 product roadmap shows stablecoin "exploration" but no live on-chain settlement.

### The Problem

* **Concrete friction**: A Fortune 500 spends \$500M+/year in cross-border vendor payments across 30+ countries. Each wire costs \$30-50 in SWIFT fees, 1-3% in FX spread, and 3-5 business days in settlement lag — during which the funds are frozen, earning nothing, and exposed to FX rate movement. A \$50M payment sitting in correspondent bank limbo for 3 days costs \~\$30K in opportunity cost alone (at 7% cost of capital).
* **Who feels this pain**: The VP of Treasury or AP/AR Controller at a Fortune 500 manufacturer, retailer, or 3PL. Concrete persona: "Lisa, VP of Treasury at a \$20B annual-revenue global retailer, managing vendor payments to 800 factories across Asia, paying \~\$15M/year in SWIFT fees and FX spread, with her team spending 40 hours/month reconciling failed and delayed wires."
* **Current workaround**: Batch SWIFT payments every Tuesday/Thursday to reduce per-transaction costs; use FX hedges (which add cost and complexity); accept 3-5 day settlement as "cost of business." Some companies use Kyriba or GTreasury for visibility but still settle via SWIFT.
* **Quantified impact**: \$17T global trade finance market. Fortune 500 cross-border B2B payments estimated at \$3-5T/year. SWIFT fees + FX spread = average 1.5% blended cost — \~\$45-75B/year in recoverable fees. Even capturing 0.1% of this flow at 0.2% fee = \~\$3-6M ARR per major enterprise customer.

### Revenue Model

* **Fee structure**: 0.1-0.25% on settled USDC volume (vs 1-3% SWIFT blended cost) — savings for the customer, margin for the platform. At \$1B in annual enterprise volume, this is \$1-2.5M ARR per customer.
* **SaaS platform fee**: \$100K-300K/year enterprise license covering ERP integration maintenance, compliance monitoring (Chainalysis AML), and SOC2 audit support. Predictable recurring revenue decoupled from volume.
* **Yield share**: During batch settlement windows (e.g., funds aggregated pre-disbursement), float is deposited into Solana yield sources (e.g., Marinade, Drift treasury vaults). Yield retained 50/50 with enterprise customer — at \$10M average float across 30 enterprise clients = meaningful basis points at scale.
* **TAM math**: \$17T trade finance market x 5% Solana-addressable share (enterprises willing to use blockchain payments in 5 years) x 0.2% take rate = \$17B TAM — \~\$1.7B realistic serviceable market at maturity. First-mover with 5 Fortune 500 anchor customers at \$1B/year each = \$5-12.5M ARR before year 3.
* **Comparable model**: Kyriba charges Fortune 500 clients \$300K-1M/year SaaS + bank fees; OpenFX pricing undisclosed but raised \$23M suggesting \$10-30M ARR target trajectory.

### Go-to-Market Friction

* **Two-sided marketplace**: Yes — corporate buyers (Fortune 500 AP teams) must pay in USDC; vendors (international suppliers) must accept USDC and off-ramp to local currency. Both sides need onboarding.
* **Cold start**: The vendor side will not onboard speculatively. The buyer must come first. Cold start requires bringing your own Fortune 500 employer as the anchor buyer — which is the specific superpower the user of this report has.
* **Bootstrap strategies**:
  * **"Be the buyer"**: The user's Fortune 500 employer is customer #1. No pitch deck — direct internal procurement. Get 3-5 top suppliers onboarded to validate the flow before external sales.
  * **Sponsored adoption**: The anchor Fortune 500 offers vendors a 2-3% early payment discount (DPO trade-off) in exchange for accepting stablecoin payment — economics are compelling enough for vendors to self-onboard.
  * **Vertical niche start**: Target a single trade lane — e.g., US retail buyer to Southeast Asian factory suppliers. Narrow geography reduces FX complexity and compliance surface area for MVP.
* **Network effects**: Once 3-5 Fortune 500 buyers onboard, Tier-1 vendors (who serve multiple Fortune 500s) see USDC payments across multiple clients — they build native USDC treasury capability — the network self-reinforces without needing to re-sell the vendor side.

### Founder-Market Fit

* **Ideal founder background**: The user of this report is the ideal founder — Fortune 500 supply chain / logistics executive with direct access to the anchor customer, credibility with CFOs and treasury teams, and domain knowledge of the specific pain (SWIFT fees, 3-5 day settlement). This is what the enterprise blockchain adoption a16z crypto essay describes as "enterprise blockchain adoption happens when someone else does the work" — you are the insider who removes the friction.
* **What they bring**: Internal champion status at anchor customer #1; knowledge of which ERP configurations matter; ability to speak "payment authorization matrix" to Fortune 500 compliance; existing vendor relationships that shorten vendor onboarding.
* **Red flags**: Do NOT build this if you're a pure crypto-native without Fortune 500 procurement relationships. The product itself is not the hard part — the hard part is getting 5 Fortune 500 AP controllers to approve a crypto-based payment system. That requires the access and credibility the user already has.
* **Team composition**: Founder (supply chain executive, BD/GTM) + 1 senior Rust/Anchor developer (Solana program architecture for multisig workflows and ERP webhooks) + 1 compliance/legal lead (FinCEN/OFAC, SOC2).

### Why Crypto/Solana?

* **What blockchain enables**: Programmable payment conditions (pay vendor X when shipment oracle confirms delivery), 24/7 settlement (no Tuesday-Thursday batch windows), float yield during settlement, instant finality at \$0.001/transaction vs \$35-50 SWIFT wire, multi-party escrow without a custodian bank.
* **Could this be built without crypto?** Yes, partially — Wise Business or Currencycloud offer faster FX. But they cannot: (1) hold funds in programmable escrow with release conditions tied to on-chain oracles, (2) pay \$0.001 per transaction enabling micro-payment and partial-payment workflows, (3) generate yield on settlement float on-chain, or (4) enable vendors to receive yield-bearing stablecoins instead of dead cash.
* **Why Solana specifically**: Sub-second finality and \$0.001 fees make high-frequency AP workflows (daily vendor payments of all sizes) economically viable. USDC's \$15B+ Solana supply provides deep liquidity. Squads Protocol provides institutional-grade multisig out of the box. Token-2022 transfer hooks enable custom compliance logic (OFAC screening, spending limits) at the protocol level. Jupiter aggregates FX routing for multi-currency settlement without a centralized FX desk.

### Risk Assessment

* **Technical risk**: Low for core payment flow — USDC transfers on Solana are battle-tested. Medium for ERP integration — SAP/Oracle connectors require partnership agreements and can take 9-18 months to certify for enterprise deployment.
* **Regulatory risk**: High but improving. Cross-border stablecoin payments from a US company to an international vendor triggers FinCEN BSA/AML requirements, OFAC sanctions screening, and potentially state money transmitter licenses. GENIUS Act (if passed) simplifies the federal framework but doesn't eliminate state licensing. Path: use Circle's Compliance API + Chainalysis for AML screening from day one; structure as a technology layer on top of Circle's licensed infrastructure rather than a money transmitter.
* **Market risk**: Painkiller, not vitamin — a Fortune 500 AP team spending \$15M/year in avoidable SWIFT fees has immediate ROI justification. The risk is not demand; it's the internal procurement approval process (legal, IT security, finance compliance) which can take 12-18 months at a Fortune 500.
* **Execution risk**: The OpenFX speed metric (\$0 to \$10B volume in under 12 months) is the most important signal here. OpenFX, Fin, and crypto-native Ripple Enterprise are all moving fast toward the Fortune 500. The window to establish a Solana-native ERP-integrated alternative is likely 12-24 months before one of these players closes the ERP integration gap.

***

## Further Reading

* **Study CargoBill** at cargobill.co — understand exactly what they've built for logistics operators; the features they don't offer are your MVP scope
* **Pantera Capital "Escape Velocity"** — the investor thesis for B2B stablecoin payments is laid out clearly
* **Squads Protocol** (squads.so) — the multisig approval infrastructure you'll build on for enterprise payment authorization workflows
* **a16z crypto's "Enterprise Blockchain Adoption"** essay — the "partner-first, enable integrators" GTM playbook is directly applicable to your situation
* **Follow OpenFX** closely — they are the most direct competitive threat on timeline; their feature gaps relative to ERP integration define your wedge


# Gaming Track: Radar vs. Renaissance
Source: https://docs.colosseum.com/copilot/examples/compare-gaming-tracks

Example: Comparing gaming track submissions, prize winners, and thematic shifts between two Colosseum hackathons

<Badge>Generated with Sonnet 4.6</Badge> · [Compare hackathons](/copilot/capabilities#use-cases)

> Compare gaming track submissions between Radar and Renaissance.

***

<Info>
  **What follows is Copilot's unedited conversational output** — the full response generated from the prompt above.
</Info>

## Renaissance vs. Radar: Gaming Track Comparison

### Volume

* **Renaissance** (Mar 2024): 214 gaming submissions
* **Radar** (Sep 2024): 279 gaming submissions (+30% growth in 6 months)

***

### Top Winners

| Place | Renaissance Gaming                                                                                                                          | Radar Gaming                                                                                                          |
| ----- | ------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| 1st   | **MeshMap + City Champ** (`meshmap-+-city-champ`) — DePIN LiDAR scanning + mixed reality gaming (\$30K)                                     | **Supersize** (`supersize`) — Real-time fully on-chain multiplayer "io" game via MagicBlock ephemeral rollups (\$25K) |
| 3rd   | **Mining Badger / Honeycomb** (`mining-badger-game-honeycomb:-resource-manager`) — On-chain crafting + game infrastructure protocol (\$15K) | **Windfall** (`windfall`) — Gamified liquid staking — DeFi/gaming crossover (\$15K)                                   |
| 5th   | **Maneko Pet** (`maneko-pet`) — Tamagotchi-style mobile game + mini-game launcher (\$5K)                                                    | —                                                                                                                     |
| 2nd   | —                                                                                                                                           | **The Arena** (`the-arena`) — PvP social trading competition — DeFi/gaming crossover (\$20K)                          |
| 4th   | —                                                                                                                                           | **Barnfight** (`barnfight`) — White-label gaming platform for communities/influencers (\$10K)                         |
| HM    | **Seternia Realms** (`seternia-realms-1`) — Fantasy RPG gamifying Solana DeFi protocols                                                     | **TrenchTown** (`trenchtown`) — On-chain trading Battle Royale with PnL jackpots                                      |
| HM    | **LePoker** (`lepoker`) — ZK + VDF poker for provably fair play                                                                             | **UNKOMON** (`unkomon-poop-to-earn`) — DePIN + gaming: biometric data → token rewards                                 |
| HM    | **Blockpal** (`blockpal`) — Trustless guild asset management (DeFi/gaming)                                                                  | —                                                                                                                     |
| HM    | **Jogojogo** (`jogojogo`) — On-chain revenue-sharing for slots, lottery, sports betting                                                     | —                                                                                                                     |

***

### Thematic Shifts from Renaissance → Radar

**Fully on-chain game logic:** Radar winners leaned hard into eliminating centralized game servers — Supersize is the flagship example, using MagicBlock for real-time state. Renaissance submissions were more traditional GameFi/NFT ownership models.

**DeFi × Gaming hybridization:** Radar saw more crossover entries (The Arena, TrenchTown) blending trading mechanics with competitive gameplay. This category barely appeared in Renaissance gaming.

**Platform plays vs. standalone games:** Radar showed more infrastructure thinking — Barnfight is a white-label platform, not just a game. Renaissance entries were more game-first.

**Mobile/casual:** Renaissance's Maneko Pet signaled mobile appetite; Radar gaming shifted toward browser-based real-time multiplayer.

**Notable builder signal:** `supersize-1` submitted to Renaissance gaming but didn't win — the same builder (`supersize`) returned for Radar and took 1st place, then entered the C2 accelerator. This persistence-to-win pattern is worth tracking.

**Archive framing:** The MagicBlock "Unblocking On-Chain Games" series ran alongside this period and directly informed the Radar gaming thesis around ephemeral rollups for real-time gaming.

**Prize pool structure:** Renaissance topped at \$30K for gaming 1st vs. Radar's \$25K, but Renaissance had fewer prize placements listed — suggesting higher concentration at the top.


# Consumer Apps for Mobile Developers
Source: https://docs.colosseum.com/copilot/examples/consumer-apps

Example: A mobile developer with no crypto experience explores consumer app opportunities on Solana

<Badge>Generated with Sonnet 4.6</Badge> · [Translate your background](/copilot/capabilities#use-cases)

> I'm a mobile developer — shipped a few apps on the App Store with 50k+ downloads. Never touched crypto before but I keep hearing about Solana being fast and cheap. What kinds of consumer apps are people building? I want something normies would actually use, not another dashboard for degens.

***

<Info>
  **What follows is Copilot's unedited deep-dive output** — the full research report generated from the prompt above.
</Info>

## Similar Projects

> **Note:** These are hackathon submissions — demos and prototypes, not production products. Many may no longer be active. They're included as inspiration and to show what's been tried before, not as a competitive landscape.

* **Trepa** (`trepa`, Breakout, 1st Place Consumer Apps) — Mobile sentiment prediction app where users stake USDC on crowd consensus rather than event outcomes. Funded by Colosseum (C3, accelerator). Built on React Native + Solana. The highest-signal proof that a mobile-first consumer Solana app can win.
* **Cron** (`cron`, Cypherpunk) — Intent-based smart wallet for P2P payments and bill splitting with no wallet addresses required. Built native iOS in Swift. Closest thing to a Venmo-style app on Solana.
* **Beamlink** (`beamlink-send-crypto-like-a-text-message`, Cypherpunk) — Send Solana tokens via shareable links through iMessage/WhatsApp without the recipient needing a wallet. Escrow-based claiming. "Onboard your grandma" was literally in their submission.
* **Bucx** (`bucx`, Renaissance, Consumer Apps) — Mobile USDC wallet for global payments using email addresses; virtual debit cards, bank on/off-ramps. Direct normie-first framing.
* **Bannga** (`bannga`, Cypherpunk) — Convert everyday consumer spending into automated USDC rewards (cashback mechanic). Explicitly targets "crypto newcomers" and "everyday spenders."
* **Decal** (`decal-payments-and-loyalty`, Breakout, 2nd Place Stablecoins) — Solana-based POS payments + token-based loyalty platform. Funded (C3, accelerator). Uses Token Extensions.
* **Swipe.fun** (`swipe.fun`, Radar) — Mobile-first consumer app for discovering and interacting with the Solana ecosystem. React Native. Targets "crypto beginners" and "mobile-first users."
* **Blockxplore** (`blockxplore`, Breakout) — Human-readable Solana block explorer, **native iPhone app in Swift/SwiftUI**, for non-technical users.

***

## Archive Insights

* **"How Stablecoins Will Eat Payments"** (a16z Crypto, Dec 2024, similarity 0.60) — Argues stablecoins are the new permissionless payment rails, and that consumer adoption follows the same S-curve as earlier internet payment waves (PayPal-on-ACH). The consumer app layer — the thing that turns raw rails into a product people use daily — is still wide open.
* **"Solana Ecosystem Report H1 2025"** (Helius, July 2025, similarity 0.69) — Solana processes 162M+ transactions/day with median fees under \$0.01; 15+ months continuous uptime since Feb 2024; 7,625 new developers joined in 2024 (83% growth). The report explicitly frames "accessibility for everyday users" as Solana's defining metric for this era.
* **"Deep Dive: State of Consumer Apps on Solana"** (Superteam, Nov 2021, similarity 0.51) — The fundamental problem: custodial wallets are the easiest onboarding but sacrifice self-custody; non-custodial wallets require seed phrase management that kills 90% of normies. The solution anticipated — embedded wallets with social login — is now production-ready (Privy, Dynamic, Crossmint all live).
* **"Backing Rain & RedotPay: Expanding the Frontiers of Stablecoin Payments"** (Galaxy Research, Apr 2025, similarity 0.59) — Documents how stablecoin payment cards achieved mainstream traction by region: Argentina (inflation hedge), India (crypto-backed credit within UPI), Southeast Asia (\$18.6B in stablecoin remittances H1 2025). Users in these markets don't think of it as "crypto" — they think of it as "my savings that keep value."
* **"Meet Crypto's Superapp: Backpack"** (Superteam, Oct 2022, similarity 0.49) — Asian super-apps (Google Pay, PhonePe, PayTM) achieved scale through payments-first distribution, then expanded. The insight: payments create daily-active-user habits that no other crypto use case achieves.

***

## Current Landscape

### Stablecoin Spend / Cashback Apps

* **Key players**: Phantom Cash (Sept 2025 launch — 15M MAU, CASH stablecoin on Solana, Visa debit card live in US Dec 2025, \$3B valuation); MetaMask Card (mUSD + Mastercard, up to 3% cashback); Rain (\$250M Series C at \~\$1.95B valuation Jan 2026, \~\$3B annualized volume)
* **Recent developments**: Monthly crypto card volume grew from \~\$100M (early 2023) to \~\$1.5B (late 2025) at 106% CAGR. GENIUS Act signed July 2025 — cashback and loyalty rewards are explicitly NOT prohibited yield. Visa USDC settlement reached \$3.5B annualized in Q4 2025.
* **Maturity**: Growing — but the consumer UX layer is still rough; big wallets bolt-on payments as a feature, not a primary product

### Live Social Game Shows with Real-Money Prizes

* **Key players**: Robinhood Trivia Live (March 2025 — 400,000 concurrent players, \$2M in Bitcoin/Doge prizes); Trepa (`trepa`, C3 Colosseum-funded, mobile sentiment prediction); no dedicated standalone app with Solana USDC prizes
* **Historical**: HQ Trivia peaked at 2.6M concurrent users before shutting down in 2020 — killed by prize distribution costs (\~2-3% PayPal fees) and Apple/Google IAP restrictions on real-money prizes
* **Maturity**: **Emerging** — one massive proof point (Robinhood event) but zero standalone products

### Family Finance & Kids' Allowance Apps

* **Key players**: Greenlight (non-crypto, \~\$4.2B valuation, 6M+ family users), Current (non-crypto teen banking)
* **Crypto adjacent**: `sona-1` (Cypherpunk, stablecoin family finance prototype), no funded crypto-native family finance app
* **Maturity**: **Emerging / Underexplored** in crypto — well-served in Web2

***

## Key Insights

* **Pattern: Consumer is the largest track but DeFi gets all the wins.** Radar + Renaissance combined show Consumer as the #1 track (58% of submissions, \~1,400 projects). Yet DeFi ruled Solana's app layer in 2025. The gap is in consumer apps that actually reach normies.
* **Pattern: The onboarding wall kills everything.** The #1 problem tag across consumer hackathon submissions is variants of "complex web3 onboarding" — 58+ projects tagged it across Cypherpunk alone. Every funded consumer app abstracts wallets away.
* **Gap: Native iOS is underrepresented.** React dominates tech stack (41% of submissions). Native Swift/iOS appears only in a handful of projects (Cron, Blockxplore). A native iOS app from someone with App Store distribution experience is a structural differentiator.
* **Gap: Live / real-time mechanics.** Nearly all consumer Solana apps are async (wallets, cashback, portfolio tools). Real-time interaction (live games, live sentiment voting) has near-zero competition and direct proof of normie demand.
* **Trend: Infrastructure is commoditizing fast.** Privy, Dynamic, and Circle Programmable Wallets now make embedded wallets trivially easy to integrate. The moat is no longer "we built the wallet" — it's "we built the thing people want to do with money."

***

## Opportunities & Gaps

* **Underexplored**: Standalone native iOS live game show / trivia app with real USDC prizes; family finance apps with stablecoin allowances and parental controls; mobile apps targeting specific geographies where stablecoins already have daily-use patterns
* **Emerging niches**: Solana-native skill games with micropayment entry fees; local merchant loyalty powered by Token Extensions; opinion/prediction games that avoid CFTC jurisdiction by rewarding crowd consensus (Trepa mechanic)
* **Well-covered**: Stablecoin wallets + debit cards (Phantom, MetaMask, Coinbase, Rain all well-funded and live); basic P2P payment apps; DeFi dashboards

***

## Deep Dive: Top Opportunity

### Native iOS Live Game Show App with USDC Prizes on Solana

### Market Landscape

* **Key players**: Robinhood Trivia Live (single-event promotional game, not a product; 400K players, \$2M prizes, March 2025); Trepa (`trepa`, Colosseum C3, funded) — crowd sentiment staking, not trivia; HQ Trivia (defunct, shut down 2020; peaked 2.6M concurrent users)
* **Landscape classification**: **Open space** — No existing standalone live game show app uses Solana/USDC as its prize/payment layer. Robinhood validated demand (400K players). Trepa validated the funded mechanic. Neither is the product described here.

> **Related Builder:** Trepa (`trepa`, C3) is building mobile sentiment prediction — stake on crowd consensus. Study their onboarding flow and how they abstract wallets for non-crypto users.

### The Problem

* **Concrete friction**: HQ Trivia shut down in 2020 with 8M registered users. The product worked. The business didn't — prize payouts cost 2–3% per transaction via PayPal; Apple/Google prohibit real-money prize apps from using in-app purchases; distributing 10,000 prizes of \$1 each cost more in PayPal fees than the prizes themselves.
* **Who experiences this**: Casual mobile gamers (18–35) who want to win real money from their couch. DraftKings has 7M monthly active users. HQ Trivia had 2.6M peak concurrent. These are normies — not crypto users.
* **Quantified impact**: HQ Trivia sold for \$0 in bankruptcy despite 8M users — a distribution asset destroyed by unit economics. As of 2026-03-06, Solana fees average under \$0.01 per transaction, making distribution of 10,000 prizes of \$0.50 each cost \~\$0.10 total in fees.

### Revenue Model

* **Mechanics**: Hybrid — free-to-play with optional paid entry for larger prize pools
  * Free tier: Small prize pools funded by sponsors/ads
  * Paid tier: Pay \$0.25–\$2.00 in USDC to enter a prize-pool game; 85–90% of entry fees go to winners, 10–15% kept as margin
  * Sponsorship: Brands sponsor rounds with custom questions — HQ Trivia's main revenue source; proven model
* **Unit economics**: 10,000 players × \$1 entry × 10% margin = \$1,000 per game. At 3 games/day = \$1.1M/year at 10K players. At 100K players: \$11M ARR.

### Go-to-Market Friction

* **Not a two-sided marketplace.** One audience: players. Game content is programmatic or curated.
* **Cold start**: Seed a prize pool with \$500–\$5,000 (founder's own money or pre-seed). Advertise 1 game event.
* **Viral loop**: "Invite 3 friends to earn an extra life" — HQ Trivia's exact mechanic drove 8M registrations with zero ad spend.

### Founder-Market Fit

* **Ideal founder**: A mobile developer who has shipped consumer apps and knows the App Store conversion funnel cold. **This is the person asking this question.**
* **What they bring**: App Store distribution (ASO, review management, conversion optimization); UI/UX sensibility for normie apps (proven by 50K+ downloads); ability to build native iOS in Swift/SwiftUI, which will make the app feel like a real game rather than a React Native wrapper.
* **Concrete advantage**: Every crypto-native trying to build this will produce a degen-looking app. A mobile dev produces something that looks like Wordle or HQ Trivia and lands in the "Games" category, not "Finance."

### Why Crypto / Solana?

* **Prize distribution**: Distributing 10,000 USDC prizes of \$0.50 costs \~\$0.01 in Solana fees. The equivalent via PayPal: \~\$500 in fees, plus KYC per recipient, plus 3–5 business day delay. This is a category change in unit economics.
* **Self-custody angle**: Winners receive USDC directly to an embedded wallet. The app never holds user funds; it's not a money transmitter.
* **GENIUS Act (July 2025)**: Cashback, prizes, and rewards paid in stablecoins are explicitly not regulated as interest.
* **Why Solana specifically**: 400ms finality means you can show live results in-game. Sub-cent fees make micropayments (under \$1 prizes) viable. Solana Mobile Stack and existing iOS SDKs (Privy supports Solana natively) lower integration complexity.

### Risk Assessment

* **Technical risk**: Low. Solana is production-stable (15+ months uptime). Privy/Dynamic embedded wallets are live in production apps.
* **Regulatory risk**: Medium. Real-money skill games are legal in 43+ US states but require careful structuring. Get an App Store gaming attorney early.
* **Market risk**: Closer to painkiller for normies who want to win real money. The risk is retention: HQ Trivia burned out quickly. Async mode, shorter sessions, and push notification strategy matter.
* **Execution risk**: Content pipeline (question quality and freshness), prize pool liquidity during early ramp, and App Store review process for real-money apps. All manageable, none fatal.

***

## Further Reading

* **Study**: Trepa's product demo and Breakout presentation (`trepa`, Breakout) — their wallet onboarding flow is the closest analog
* **Read**: "How Stablecoins Will Eat Payments" (a16z, Dec 2024) — the consumer adoption curve and what it took for prior payment rails to cross the normie chasm
* **Explore**: Privy's embedded wallet docs — the fastest path to "no wallet visible to the user" on Solana


# MEV Batch Auctions
Source: https://docs.colosseum.com/copilot/examples/mev-batch-auctions

Example: Evaluating batch auction execution infrastructure to eliminate MEV on Solana

<Badge>Generated with Sonnet 4.6</Badge> · [Challenge a thesis](/copilot/capabilities#use-cases)

> My thesis is that Solana doesn't need another DEX — it needs better execution infrastructure. I want to build a batch auction system that eliminates MEV for retail traders. Think CowSwap but native to Solana's architecture. Has anyone tried this?

***

<Info>
  **What follows is Copilot's unedited deep-dive output** — the full research report generated from the prompt above.
</Info>

## Similar Projects

> **Note:** These are hackathon submissions — demos and prototypes, not production products. Many may no longer be active. They're included as inspiration and to show what's been tried before, not as a competitive landscape.

* **Archer Exchange** (`archer-exchange`, Cypherpunk, 4th Place DeFi, **C4 Accelerator**) — The closest match to your thesis: an MEV-resistant exchange primitive using **dual flow batch auctions (DFBA)**, the exact mechanism proposed by Jump Crypto. Built by a team of 3, Anchor/Rust on Solana. Now in the Colosseum accelerator.
* **URANI** (`urani`, Renaissance, **1st Place DeFi & Payments, C1 Accelerator**) — Intent-based swap aggregator with batch auction MEV mitigation and a solver/searcher marketplace. Positive-sum design across traders, market makers, and searchers.
* **DARKLAKE** (`blackpool`, Radar, 2nd Place DeFi, **C2 Accelerator**) — ZK-proof-based MEV-resistant DEX on Solana using private order matching; different technical approach (encryption vs. batching) but same goal.
* **Fair Swap** (`fair-swap`, Cypherpunk) — MEV-resistant DEX on Solana using fair batch auctions with on-chain transparency; Rust/Anchor implementation.
* **Fairswap** (`fairswap`, Radar) — Sandwich-resistant AMM using slot-based state reset: no swap executes at a price more favorable than the pool state at start of slot.
* **Stormbreaker** (`stormbreaker`, Radar) — Sandwich-resistant AMM; AMM design approach to MEV resistance rather than auction mechanism.
* **Mato** (`mato`, Breakout, Honorable Mention DeFi) — DEX with a time-weighted order book for continuous streaming execution; MEV protection through temporal smoothing rather than discrete batches.

***

## Archive Insights

* **"Solana MEV Report: Trends, Insights, and Challenges"** (Helius, Jan 2025) — The canonical Solana MEV reference. Confirms that Solana's streaming block production and lack of global mempool create a structurally different MEV environment than Ethereum. The DeezNode sandwich bot alone extracted 65,880 SOL (\~\$13.4M) in 30 days. Validates the urgency of the problem.
* **"MEV Explained"** (a16z Crypto, May 2025) — Taxonomy of MEV mitigations: order flow auctions, batch auctions, threshold encryption, fair sequencing. Frames batch auctions as one of the most theoretically sound approaches because uniform clearing prices structurally remove the incentive to reorder transactions.
* **"Orderbook & Matching"** (Drift Docs, updated Feb 2026) — Drift's live JIT (Just-in-Time) auction is the closest existing Solana-native analog: a 5-second window where market makers can fill taker orders before they hit the AMM. Evidence that auction mechanisms are already in production on Solana.
* **"Gradual Dutch Auctions"** (Paradigm, April 2022) — Foundational research on auction mechanisms for on-chain price discovery. Conceptual grounding for the uniform-price auction primitives that underpin both DFBA and CoW's batch model.

***

## Current Landscape

### Angle 1: Batch Auction MEV Elimination (the CoW Swap analog)

* **Key players**: CoW Protocol (EVM-only, top-3 DEX aggregator in 2025, \~\$10B/month volume); Archer Exchange (C4, Solana-native DFBA prototype); Ellipsis Labs/Plasma (Solana, application-layer sandwich-resistant AMM, \$20M Series A from Paradigm)
* **Recent developments**: Jump Crypto published the DFBA paper in **August 2025** — two independent Maker/Taker auctions every 100ms with a single clearing price. Ellipsis Labs raised \$20M from Paradigm and shipped Plasma (audited, deployed on Solana mainnet). Archer Exchange entered C4 in 2025 building directly on the DFBA paper.
* **Maturity**: Growing — active research, first funded companies emerging, but no production batch auction execution layer on Solana exists yet

### Angle 2: Intent / Solver Architecture as MEV Abstraction

* **Key players**: URANI (C1, intent aggregator); Jupiter (dominant aggregator, no explicit MEV protection); Pyth Express Relay (live on mainnet — priority auction for liquidations, not swaps); Mantis Protocol (SVM rollup with IBC, intent-based)
* **Recent developments**: Pyth Express Relay is live with searchers including Flow Traders, Wintermute, Auros. NEAR Intents grew from \$3M to \$6B cumulative volume in 2025. CoW Swap's solver competition model now processes \$10B/month.
* **Maturity**: Growing — solver/intents model is validated on EVM, not yet a first-class Solana-native primitive

### Angle 3: Validator-Level MEV Mitigation (Protocol Infrastructure)

* **Key players**: Jito (Jito-Solana client, bundles, live); Paladin (modified validator client with anti-sandwich + priority port, early access); Multiple Concurrent Leaders (MCL, SIMD-level research, years away)
* **Recent developments**: Jito suspended public mempool March 2024, causing DeezNode-style private mempools to proliferate. 2025 coordinated validator action cut sandwich profitability 60-70% but problem persists.
* **Maturity**: Established (Jito) + Emerging (Paladin, MCL)

***

## Key Insights

* **The CowSwap gap on Solana is real but crowded at the DEX layer**: Three accelerator companies (Archer C4, URANI C1, DARKLAKE C2) have built MEV-protective DEXs on Solana. The consumer-facing DEX version of your thesis is actively being executed.
* **No one has built the infrastructure layer**: Existing attempts are all single-protocol DEXs. Nobody has built the CoW *Protocol* equivalent — a solver/batch-settlement layer that Jupiter, Orca, and Raydium route *through*, capturing MEV protection across all Solana order flow.
* **Jump Crypto's DFBA paper is fresh theoretical firepower**: Published August 2025, this is the first rigorous formalization of a batch auction mechanism tuned for Solana's streaming block production.
* **Solana's architecture creates both a challenge and an opportunity**: No global mempool means private mempools dominate sandwiching. Streaming block production means batch windows must be sub-second. These constraints mean EVM solutions can't port over — the field is open.
* **\$370-500M extracted in 16 months** is the lower-bound TAM proxy for value that a protective execution layer could recapture.

***

## Opportunities & Gaps

* **Infrastructure play (underexplored)**: A batch-settlement execution layer that aggregates order flow from existing Solana DEXs/AMMs — not a DEX itself, but a routing layer beneath Jupiter. Highest-leverage angle with no funded company building it.
* **DFBA as a shared primitive**: The Jump Crypto DFBA mechanism designed as an open protocol that DEXs can adopt, with solver economics that attract market makers.
* **Retail-specific execution guarantee**: A slippage-guarantee product for memecoin/retail traders who currently set dangerously high slippage tolerances.
* **Well-covered at the DEX layer**: Building another MEV-resistant DEX faces three funded accelerator companies. Differentiation needs to be architectural.

***

## Deep Dive: Top Opportunity — Solana Batch Execution Infrastructure Layer

### Market Landscape

* **Key players**: Ellipsis Labs (\$20M from Paradigm — Phoenix DEX, Plasma AMM, Gavel); Archer Exchange (C4, DFBA prototype); URANI (C1, intent aggregator); Jupiter (dominant order routing, no native MEV protection); Jito (MEV infrastructure via bundles)
* **Landscape classification**: **Differentiation opportunity — Integration.** Existing players operate as standalone DEXs or validator clients. None compose as a routing/settlement layer beneath existing DEX aggregators.

> **Related Builder:** Archer Exchange (`archer-exchange`, C4) is building DFBA on Solana. Study their GitHub (`Archer-Exchange/toy-dfba`). To differentiate: they're building a vertical DEX product; the opportunity is building the horizontal infrastructure layer that Archer itself could eventually route through.

### The Problem

* **Concrete friction**: A retail trader swapping a memecoin on Raydium with 5% slippage tolerance is guaranteed to lose \~\$8-9 on average per trade to sandwich bots (DeezNode average: \$8.67/attack). With 1.55M sandwich transactions in 30 days from one bot alone, this is routine.
* **Who feels it**: Memecoin retail traders are the primary victims. Helius confirms they are "relatively insensitive" to frontrunning awareness — they don't know they're being sandwiched.
* **Quantified impact**: \$370-500M extracted from Solana users over 16 months. DeezNode alone annualizes to \~\$160M/year from a single bot.

### Revenue Model

* **How it makes money**: Protocol fee on order flow that routes through the batch settlement layer — e.g., 1-2 bps per trade. This is below the cost of MEV they'd otherwise pay.
* **TAM math**: Solana DEX volume \~\$50-100B/month. If the infrastructure layer captures 10% of routing at 1 bps: \$5-10M/month (\$60-120M/year). CoW Protocol comparison: \$10B/month volume on EVM.

### Go-to-Market Friction

* **Two-sided marketplace**: Yes — order flow from DEXs/aggregators on one side, solvers/market makers on the other.
* **Bootstrap strategies**: Be the first solver yourself for 6-12 months. Start with one niche (memecoin trades, highest sandwich exposure). Anchor with existing market makers already participating in Pyth Express Relay (Flow Traders, Wintermute, Auros).

### Founder-Market Fit

* **Ideal background**: Deep MEV knowledge (Jito bundles, private mempools, slot structure) + existing market maker relationships + Solana protocol-level experience (Anchor, Rust, SVM internals).
* **Red flags**: Don't build this if you've only worked on EVM — Solana's streaming architecture fundamentally changes batch window design.
* **Team composition**: Protocol engineer (Rust/SVM), MEV/markets specialist, one BD role with market maker relationships.

### Why Crypto/Solana?

* **What blockchain enables**: A permissionless solver network, cryptographic batch settlement guarantees, composability across protocols.
* **Why Solana specifically**: Sub-second finality is a prerequisite for a batch layer that doesn't destroy UX. On Ethereum, 30-second batch windows work (CoW). On Solana, users expect sub-second execution — your batch window must be 200-400ms. This constraint makes Solana-native design non-negotiable.

### Risk Assessment

* **Technical risk**: High. Fitting a full batch auction inside Solana's \~400ms slots is non-trivial. Drift's JIT auction works because it's embedded in their own protocol.
* **Regulatory risk**: Low-moderate. The batch layer doesn't custody funds; it's a routing/settlement protocol.
* **Market risk**: Painkiller, but the pain is invisible to retail traders. Risk that coordinated validator action reduces the problem before you ship.
* **Execution risk**: Convincing Jupiter or a mid-tier DEX to route through your batch layer before proven volume is the classic distribution moat problem.

***

## Further Reading

* **Archer Exchange GitHub** (`Archer-Exchange/toy-dfba`) — The only open-source DFBA implementation on Solana.
* **Jump Crypto DFBA Paper** (August 2025) — The theoretical foundation for 100ms batch windows.
* **Ellipsis Labs Plasma** — Study their application-layer approach and where it leaves room for an infrastructure play.
* **Helius MEV Report** (Jan 2025) — Required reading for Solana MEV landscape.
* **Pyth Express Relay docs** — Study the solver/searcher architecture for an analogous bootstrap playbook.


# Privacy-Preserving Stablecoin
Source: https://docs.colosseum.com/copilot/examples/privacy-stablecoin

Example: Researching privacy-preserving stablecoins with ZK proofs on Solana

<Badge>Generated with Sonnet 4.6</Badge> · [Research concepts](/copilot/capabilities#use-cases)

> I want to build a privacy-preserving stablecoin — like a Zcash-style shielded pool but for USDC on Solana. Users deposit USDC, get a private balance, and can transfer without anyone seeing amounts or recipients. I know Tornado Cash got sanctioned but I think there's a compliant way to do this with selective disclosure and ZK proofs. What does the landscape look like and is this even possible on Solana technically?

***

<Info>
  **What follows is Copilot's unedited deep-dive output** — the full research report generated from the prompt above.
</Info>

## Similar Projects

> **Note:** These are hackathon submissions — demos and prototypes, not production products. Many may no longer be active. They're included as inspiration and to show what's been tried before, not as a competitive landscape.

* **Hush** (`hush`, Breakout) — ZK-proof protocol for anonymous token transfers on Solana using Groth16; multi-track (Consumer, DeFi, Infrastructure)
* **noirwire** (`noirwire`, Cypherpunk) — Private payments + encrypted messaging using shielded pools and the Noir ZK language on Solana; closest architectural match to Zcash-style design
* **Privax Protocol** (`privax-protocol`, Breakout) — "Banking secrecy" self-custody layer with ZK proofs + "compliant transactions"; 19 likes / 17 comments, highest engagement in the cluster; explicitly targets regulatory compliance
* **NinjaPay** (`ninjapay`, Breakout) — ZK + stealth addresses + "auditable back keys for lawful oversight"; explicitly embeds compliance from day one
* **Radr** (`radr`, Cypherpunk) — ZK-SNARK privacy pool for SOL with multi-hop relaying and on-chain Merkle tree verification; technically close to the note-commitment tree approach in Zcash
* **Cloak** (`cloak-or-solana-privacy-layer`, Cypherpunk, **3rd Place Stablecoins, C4 Accelerator**) — Token-mixing privacy layer with miner-driven anonymity sets; NOT ZK-proof-based — uses mixer/incentivized-mining model
* **DARKLAKE** (`blackpool`, Radar, **2nd Place DeFi, C2 Accelerator**) — ZK private DEX (trade privacy + MEV protection), not a stablecoin shielded pool; adjacent vertical
* **Degen Cash** (`degen-cash`, Cypherpunk, **C1 Accelerator**) — Gamified privacy-preserving stablecoin using Arcium MPC for confidential transfers; uses USDC + randomized mint/burn mechanics

***

## Archive Insights

* **"Achieving Crypto Privacy and Regulatory Compliance"** (a16z, Burleson/Korver/Boneh, 2022, similarity 0.565) — Proposes a three-layer ZK compliance framework: (1) deposit screening against sanction blocklists, (2) withdrawal screening, (3) selective de-anonymization via ZK proofs for law enforcement. Written in the wake of the Tornado Cash sanction. Directly validates the user's thesis.
* **"Privacy-Protecting Regulatory Solutions Using Zero-Knowledge Proofs" (Full Paper)** (a16z, 2022, similarity 0.552) — The full academic companion. Argues privacy-preserving protocols that lack adequate controls fail from insufficient compliance architecture, not from privacy itself.
* **"6 Myths About Privacy on Blockchains"** (a16z, Sverdlov/Slavin, 2025, similarity 0.693) — Most relevant result. Argues the "privacy vs. compliance" tension is a false dichotomy; ZK proofs, homomorphic encryption, and MPC are mature enough to give users privacy while giving regulators the signals they need.
* **"Contracts with Bearer"** (Nick Szabo / Nakamoto Institute, 1997/1999, similarity 0.259) — Foundational framing: digital bearer certificates as the cryptographic primitive for private value transfer. Shielded USDC is the 2025 incarnation of what Szabo described.
* **"Breakpoint 2023: Composable Privacy with Sandwiching"** (Breakpoint transcripts, 2023, similarity 0.363) — Solana-specific talk on composable privacy layers using "sandwiching" patterns — wrapping existing token programs with privacy layers rather than replacing them. Architecturally relevant for USDC / Token-2022 integration.

***

## Current Landscape

### Angle 1: Solana-Native Privacy Infrastructure (Technical Feasibility)

* **Key players**: Solana Confidential Balances (Token-2022, Solana Labs), Arcium (\$9M raised, Solana Mainnet Alpha Feb 2026), Bonsol (ZK co-processor, in development)
* **Recent developments**: Solana launched Confidential Balances in April 2025 — hides transfer *amounts* via homomorphic encryption + ZK proofs, with optional "Auditor Key" that can decrypt amounts for compliance. Arcium launched Mainnet Alpha February 2, 2026. Confidential SPL standard targeted for Q1 2026.
* **Maturity**: Growing — native infrastructure exists, production apps emerging in 2026

### Angle 2: Compliance-First Privacy Protocols (Regulatory Path)

* **Key players**: Umbra (Arcium-powered, \$155M ICO commitments, Feb 2026), Midnight (Cardano partner-chain, ZK + selective disclosure), Aztec (EVM L2 for private smart contracts), Circle/Aleo partnership (privacy USDC on Aleo, not Solana)
* **Recent developments**: Tornado Cash sanctions reversed by OFAC March 2025 after Fifth Circuit ruling (immutable smart contracts not "property" under IEEPA). Roman Storm trial resulted in hung jury on two counts (Aug 2025). zkKYC pattern now mainstream.
* **Maturity**: Emerging — regulation has clarified meaningfully, compliance-first architecture is understood but sparse in production

### Angle 3: Institutional DeFi Privacy (B2B Use Case)

* **Key players**: Fireblocks (KYC-gated vaults, institutional DeFi), Sygnum Bank (institutional DeFi analysis)
* **Recent developments**: Georgetown Law Oct 2025 paper on illicit finance risk in institutional DeFi. Sygnum report: institutional DeFi infrastructure exists but allocation hasn't followed — compliance gap is the stated blocker.
* **Maturity**: Emerging — demand exists, infrastructure inadequate, winner not determined

***

## Key Insights

* **The "amount-only" gap**: Solana's native Confidential Balances (Token-2022) hides amounts but *not sender/recipient*. On-chain you can still see who is sending to whom — just not how much. A full Zcash-style shielded pool is NOT natively available and requires a separate program.
* **Umbra is the closest competitor but barely started**: Launched Feb 2026 in closed beta with 100 users/week and a \$500 deposit cap. Uses MPC (not pure ZK), which has different trust assumptions. Compliance features are minimal.
* **The compliance angle is the differentiator**: Every privacy project in the hackathon corpus treats compliance as an afterthought. The a16z paper from 2022 laid out the blueprint — nobody has built it fully on Solana.
* **Elusiv is dead** (sunset Jan 2025), Cloak uses a mixer model (legally riskier post-Tornado Cash), DARKLAKE is a DEX not a stablecoin pool.
* **Trend**: Privacy + compliance is converging. The 2025-2026 window is optimal: Tornado Cash sanctions reversed, Solana native ZK infrastructure mature, institutional demand explicitly expressed.
* **Cohort data**: "Lack of financial privacy" is NOT in the top 8 problem tags across cypherpunk+breakout (2,992 total projects) — the space is *underrepresented* relative to its importance.

***

## Opportunities & Gaps

* **Underexplored**: Compliance-first ZK stablecoin infrastructure for regulated businesses and institutions — specifically the BSA/AML stack layered on top of a full shielded pool
* **Underexplored**: USDC-native shielded pool via Circle partnership — no major protocol has become "the official private USDC layer"
* **Emerging niche**: B2B private payments on Solana (payroll, supplier payments, treasury management) — institutions can't use public chains, can't use Umbra (no compliance stack), no alternative
* **Saturated**: Generic "privacy mixer" approach — regulatory risk, no differentiation
* **False start**: Trying to build on Arcium/MXE as a middleware play — Umbra already occupies this with \$155M backing

***

## Deep Dive: Top Opportunity

**Compliance-First ZK Stablecoin Pool for Regulated Entities on Solana**

### Incumbent Analysis

> **Direct Competitor Alert:** **Umbra** (Arcium-powered, launched Feb 2026) is building a "dual-mode shielded environment" with selective disclosure via viewing keys. They have \$155M in ICO commitments. To differentiate, you need a concrete wedge.

However, the gap is **real** — it is a **Partial gap (Segment)**:

* **Who is the incumbent?** Umbra + Arcium for general-purpose shielded finance; Token-2022 Confidential Balances for amount-only privacy. No incumbent for regulated/institutional USDC privacy.
* **Gap classification**: Umbra serves **privacy-first crypto-native users**. It does not serve **regulated businesses** who need: (1) BSA/AML-compatible transaction monitoring, (2) Travel Rule compliance, (3) zkKYC-gated entry, (4) structured audit reports for regulators. Umbra explicitly avoids this complexity.
* **Evidence**: Sygnum Bank May 2025: "institutional DeFi infrastructure exists but allocation hasn't followed — compliance gap is the stated blocker."

### The Problem

* **Concrete friction**: A DAO paying 12 contractors monthly in USDC exposes salary bands, vendor relationships, and treasury allocation on a public ledger. A pharmaceutical company paying clinical trial sites can't use Solana because competitors can monitor payments. A market maker can't execute treasury transfers without broadcasting position changes.
* **Who experiences this?** B2B payment operations teams at crypto-native companies; regulated financial institutions exploring Solana; individual high-net-worth users who need privacy from business competitors.
* **Quantified impact**: Cross-border B2B payments: \$150T/year global. DeFi TVL on Solana: \~\$8B. Even 0.1% of global B2B payment flow is \$150B/year.

### Revenue Model

* **Transaction fee**: 0.1-0.2% per shielded transfer
* **Compliance SaaS**: \$500-5,000/month per entity for AML monitoring dashboard, audit reports, regulator access
* **White-label SDK**: License the compliance-ready shielded pool to other DeFi protocols
* **TAM path**: 1,000 enterprise accounts × \$1,000/month = \$12M ARR recurring, plus transaction fees

### Go-to-Market Friction

* **Cold start problem**: The anonymity set problem — if only 10 people use the pool, withdrawals are trivially deanonymized. Must be solved before launch.
* **Bootstrap**: Seed with \$500K-2M protocol-owned USDC. Sign 3-5 DAOs with active payroll as design partners. Leverage Solana Foundation privacy grants.
* **Integration targets**: Squads (multisig) and Realms (DAO treasury) — natural entry points for B2B/DAO payroll.

### Founder-Market Fit

* **Ideal background**: Former Chainalysis/TRM compliance engineering, or a bank BSA officer who has also shipped on-chain protocols.
* **Red flags**: A pure crypto-privacy maximalist who views compliance as ideological compromise. Also: someone without ZK engineering experience.
* **Team**: ZK engineer + compliance/legal person + growth/BD for DAO/institution relationships. Three people minimum.

### Risk Assessment

* **Technical risk**: Moderate. ZK proof generation is well-understood, but Zcash-style full anonymity on Solana's account model requires careful engineering. Budget 6-9 months for production-ready proving system.
* **Regulatory risk**: Nuanced. Tornado Cash sanctions reversed March 2025; a16z/Dan Boneh framework has regulatory legitimacy. But Roman Storm still facing one guilty count. FATF Travel Rule applies. The compliance features are not just marketing — they are your legal moat.
* **Market risk**: Painkiller for B2B payroll operations. Behavioral inertia is real — need a specific activation event to accelerate adoption.
* **Execution risk**: Getting a BSA officer at a regulated institution to sign off on using a smart-contract-based privacy pool is a high-friction sales cycle. Start with DAOs where the compliance bar is lower.

***

## Further Reading

* **Helius blog: "Confidential Balances — Empowering Confidentiality on Solana"** — Technical deep dive on Token-2022 architecture
* **a16z full paper: "Privacy-Protecting Regulatory Solutions Using Zero-Knowledge Proofs"** — The academic blueprint for your compliance feature set
* **Projects to study**: `noirwire` (Noir-based ZK on Solana), `privax-protocol` (highest community engagement), `ninjapay` (compliance-first with auditable back keys)
* **Communities**: Solana privacy working group, Arcium developers (understand their MXE model as your primary technical competitor)


# FAQ
Source: https://docs.colosseum.com/copilot/faq

Frequently asked questions about Colosseum Copilot

## How do I get a PAT?

Free for all Colosseum Arena members.

Log in to [Colosseum Arena](https://colosseum.com/arena/copilot) and generate a token. Set two environment variables:

```bash theme={null}
export COLOSSEUM_COPILOT_API_BASE="https://copilot.colosseum.com/api/v1"
export COLOSSEUM_COPILOT_PAT="your-token-here"
```

See [Getting Started](/copilot/getting-started) for full setup instructions.

## Which tools are supported?

| Tool        | Status    | Install method                                              |
| ----------- | --------- | ----------------------------------------------------------- |
| Claude Code | Supported | `npx skills add ColosseumOrg/colosseum-copilot`             |
| Codex       | Supported | `npx skills add ColosseumOrg/colosseum-copilot -a codex`    |
| OpenClaw    | Supported | `npx skills add ColosseumOrg/colosseum-copilot -a openclaw` |

## What are the rate limits?

See [API Reference](/copilot/api-reference#rate-limits) for the full rate limit table.

## What happens when my idea already exists?

Copilot tells you directly. It runs incumbent validation and classifies the gap:

* **Full gap**: nobody has addressed this problem
* **Partial gap**: incomplete coverage (segment, UX, geographic, pricing, or integration)
* **False gap**: already solved

If an existing project is building the same thing, you get told immediately with the project name, hackathon, and what they've shipped. Copilot won't say "there's room for both" without evidence.

## Is my research data private?

Yes. Query content and results are never stored, shared, or used for training. We log request metadata (route, status code, latency) for reliability monitoring, but your actual queries and responses are not persisted.

## How current is the data?

* **Hackathon projects** update after each Colosseum hackathon
* **Archive sources** refresh on varying intervals (protocol docs within days, historical archives are static)
* **The Grid** provides crypto ecosystem metadata
* **Web search** is live
* **Breakpoint transcripts** are added after each annual conference

The eval suite tests for freshness. Responses are expected to cite data within 6 months.

## What's the difference between conversational and deep dive mode?

**Conversational** (default): Answers questions with targeted API calls and inline citations. Fast, concise, evidence-backed. Good for lookups, comparisons, and quick assessments.

**Deep dive** (explicit opt-in): Full 8-step research workflow with parallel data gathering, incumbent validation, gap classification, and a structured report including revenue model, GTM strategy, and risk assessment. Activates when you say "vet this idea", "deep dive", or "should I build X?"

## Can I use the API directly without the skill?

Yes. The skill file is a prompt that teaches your coding assistant how to use the API effectively, but the underlying REST endpoints work with any HTTP client. See [API Reference](/copilot/api-reference) for curl examples.

## What if my query returns no results?

Archive search auto-cascades through three retrieval tiers (vector → chunk text → document text) before returning empty. If you still get no results:

* Try conceptual synonyms (e.g., `"prediction markets"` → `"futarchy"`)
* Broaden the query (3–6 keywords work best)
* Remove filters that may be too restrictive
* Check if the topic exists in the corpus (some niche areas may not have coverage yet)

## Does Copilot write code?

No. Copilot is a research tool, not a code generator. It helps you understand the landscape — what's been built, who's funded, where the gaps are — so you build the right thing. It runs inside your coding assistant but doesn't produce Solana programs or smart contracts.

## Does Copilot replace doing my own research?

No. Think of it as a starting point that covers ground faster than you can manually. Copilot searches structured datasets and curated archives, but you should always verify the current status of projects and market data independently. Hackathon submissions are demos and prototypes — not all become active products.

## How is this different from asking ChatGPT about Solana?

Data access. General-purpose LLMs don't have structured access to 5,400+ Colosseum hackathon submissions, 84,000+ curated archive documents, or The Grid's ecosystem metadata. Copilot's evidence floors also mean every claim must trace to a specific source — it won't fill gaps with speculation.

## How do I report issues or suggest sources?

Use the [`POST /feedback`](/copilot/api-reference#post-colosseumcopilotfeedback) endpoint — your agent can call this automatically when it encounters issues. You can also reach out in the [Colosseum Discord](https://colosseum.com/discord).

To suggest a new archive source, use [`POST /source-suggestions`](/copilot/api-reference#post-colosseumcopilotsource-suggestions) or see [Archive Corpus: Source freshness and suggestions](/copilot/archive-corpus#source-freshness-and-suggestions).


# Getting Started
Source: https://docs.colosseum.com/copilot/getting-started

Get from zero to your first Copilot query in under 5 minutes

## 1. Get a Personal Access Token

Log in to [Colosseum Arena](https://colosseum.com/arena/copilot) and generate a PAT. The token is shown once. Copy it immediately and store it securely.

## 2. Set environment variables

```bash theme={null}
export COLOSSEUM_COPILOT_API_BASE="https://copilot.colosseum.com/api/v1"
export COLOSSEUM_COPILOT_PAT="your-token-here"
```

Add these to your shell profile (`.zshrc`, `.bashrc`, etc.) so they persist across sessions.

## 3. Install the skill

<Tabs>
  <Tab title="Claude Code">
    ```bash theme={null}
    npx skills add ColosseumOrg/colosseum-copilot
    ```
  </Tab>

  <Tab title="Codex">
    ```bash theme={null}
    npx skills add ColosseumOrg/colosseum-copilot -a codex
    ```
  </Tab>

  <Tab title="OpenClaw">
    ```bash theme={null}
    npx skills add ColosseumOrg/colosseum-copilot -a openclaw
    ```
  </Tab>
</Tabs>

## 4. Verify the connection

```bash theme={null}
curl "$COLOSSEUM_COPILOT_API_BASE/status" \
  -H "Authorization: Bearer $COLOSSEUM_COPILOT_PAT"
```

You should see a JSON response like `{ "authenticated": true, "expiresAt": "...", "scope": "..." }`.

## 5. Run your first query

Open your coding assistant and ask:

> What Solana hackathon projects have worked on gasless transactions?

Copilot will search the project corpus and return a concise list with project slugs and descriptions.

For a deeper analysis, try:

> I want to build a privacy-preserving stablecoin on Solana. Vet this idea.

This triggers the full 8-step deep research workflow: parallel searches across projects, archives, and web; incumbent validation; gap classification; and a structured opportunity report.

Your token expires after 90 days. See [Authentication](/copilot/authentication) for details.

## Troubleshooting

**400 Invalid JSON**: Your request body contains malformed JSON. Check for syntax errors, trailing commas, or unescaped characters.

**401 Unauthorized**: Your PAT is missing, expired, or malformed. Generate a new one at [/arena/copilot](https://colosseum.com/arena/copilot).

**413 Payload Too Large**: Your request body exceeds the 1 MB size limit. Reduce the payload size.

**429 Too Many Requests**: You've hit a rate limit. See [API Reference](/copilot/api-reference) for limits. Most agent runtimes serialize overflow automatically.

**Skill not loading**: Ensure the skill file is in the correct location for your tool. For Claude Code, verify with `claude skill list`.

## Keeping the skill up to date

Run `npx skills update` to pull the latest version. The skill also checks automatically: after your first API call, it compares its local version against the `X-Copilot-Skill-Version` response header and notifies you if an update is available.


# Colosseum Copilot
Source: https://docs.colosseum.com/copilot/introduction

A research skill that turns your AI coding assistant into a Solana startup analyst

Copilot gives your agent direct access to:

* **5,400+ hackathon project submissions** with tech stack, problem/solution tags, and competitive context
* **84,000+ archive documents** across 65+ curated sources: cypherpunk literature, protocol docs, investor research, founder essays
* **Hackathon analytics** across every Colosseum hackathon (Renaissance, Radar, Breakout, Cypherpunk)
* **6,300+ products across crypto** from [The Grid](https://thegrid.id/), ecosystem metadata
* **Web search** for current competitive landscape

<Card title="Ecosystem data by The Grid" icon="https://mintlify.s3.us-west-1.amazonaws.com/colosseum/copilot/%3Csvg%20xmlns=%22http:/www.w3.org/2000/svg%22%20width=%22372%22%20height=%22402%22%20viewBox=%220%200%20372%20402%22%20fill=%22none%22%20className=%22h-6%20w-6%22%3E%3Cpath%20d=%22M0%20401.955H71.7924C71.7924%20277.456%20160.08%20201%20299.107%20201H372.222V0H299.107C299.107%20124.5%20210.382%20201%2071.7924%20201H0V402V401.955Z%22%20className=%22fill-black%20dark:fill-white%22%20/%3E%3C/svg%3E" href="https://thegrid.id/">
  6,300+ products across crypto — powered by The Grid
</Card>

## What makes it different

**Honest about competition.** If another team is already building the exact same thing, Copilot tells you immediately — with the project name, hackathon, and what they've shipped.

**Gap classification.** When incumbents exist, Copilot classifies the gap:

* **Full gap**: nobody has addressed this problem
* **Partial gap**: incomplete coverage (segment, UX, geographic, pricing, or integration)
* **False gap**: already solved

**Evidence floors.** Every answer must meet minimum evidence requirements. A market assessment needs builder project data, at least one archive citation, and current landscape evidence. If Copilot can't meet the floor, it says so rather than filling the gap with speculation.

**Curated archive dataset.** The archive draws from 65+ hand-selected sources: the Cryptography Mailing List (1990s), Satoshi's emails, Nick Szabo's essays, Solana Breakpoint transcripts (2022–2025), and research from Paradigm, a16z, Multicoin, Pantera, Galaxy, and more.

## See it in action

Ask Copilot: *"I work in logistics at a Fortune 500. We spend millions on cross-border payment fees. Is anyone doing stablecoin-based trade finance on Solana?"*

Copilot immediately surfaces CargoBill (Colosseum Accelerator C3, 1st Place Stablecoins) as the closest predecessor, classifies the gap as **Partial — Segment** (CargoBill targets freight forwarders, not Fortune 500 buyers), identifies funded competitors (OpenFX at $23M, Fin at $17M), and recommends a specific wedge: an ERP-integrated stablecoin treasury module targeting the corporate AP side.

Every claim traces to a named project, archive source, or data point. See the [full unedited output](/copilot/examples/b2b-stablecoin-payments) and [five more examples](/copilot/examples).

## How it works

Copilot operates in two modes:

1. **Conversational** (default): Answer questions with targeted API calls and inline citations. Fast, concise, evidence-backed.
2. **Deep Dive** (explicit opt-in): Full 8-step research workflow: parallel data gathering across projects, archives, and web; hackathon analysis; incumbent validation; gap classification; opportunity ranking; and a structured report with revenue model, GTM strategy, and risk assessment.

Deep dive activates when you say "vet this idea", "deep dive", "full analysis", "validate this", "should I build X?", or "is X worth building?" — or when you accept Copilot's offer to go deeper.

## Evaluated against real prompts

Copilot is rigorously evaluated against a suite of prompts covering DeFi lending, MEV protection, prediction markets, AI agent payments, privacy infrastructure, DePIN skepticism, cross-domain synthesis, and empty-result handling.

See [Examples](/copilot/examples) for annotated prompt/response pairs from evaluation runs.

Copilot supports **Claude Code**, **Codex**, and **OpenClaw**. See [Getting Started](/copilot/getting-started) to set up in under 5 minutes.