> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/api-reference/architecture-v2.1-apis.md).

# Architecture v2.1 APIs

These endpoints expose the operational-correctness model shared by web, Studio, backend and future mobile clients.

## Architecture and source of truth

```
GET /api/v1/architecture
```

Returns Architecture v2.1, bounded contexts, authoritative-state matrix, core authority rule and formal transition maps.

## Feature/deployment registry

```
GET /api/v1/features
```

Feature status and deployment status are separate. Sanitized public deployment configuration can be returned; private authorities and credentials never appear in this response.

## Action Registry

```
GET  /api/v1/actions/definitions
POST /api/v1/actions/preflight
POST /api/v1/actions
```

Preflight validates feature enablement, subject validity, actor eligibility, destination verification, permitted amount, network and supported currency before transaction preparation. Action creation is durable and idempotent.

## Releases

```
GET  /api/v1/releases
POST /api/v1/releases
POST /api/v1/releases/:id/status
```

Release status changes are checked against the formal transition map. Invalid jumps are rejected.

## Policy versions

```
POST /api/v1/policies
GET  /api/v1/policies/:policyId/current
```

Policy versions are immutable references identified by policy ID, integer version and content hash. Historical commercial/reward outcomes snapshot the versions/hashes they used.

## Discovery and creator graph

```
GET  /api/v1/discover
GET  /api/v1/creator-graph/:creatorId
POST /api/v1/creator-graph/relations
```

Discovery covers music, creators, projects, Marketplace, communities, challenges and campaigns. Search ranking factors are not the leaderboard score.

## Explainable leaderboard

```
GET /api/v1/leaderboard/me/explain
```

Returns an authoritative scoring snapshot when one exists, including policy/window context and legitimate score factors. The API does not fabricate a score when no snapshot exists.

## Attribution

```
POST /api/v1/attribution
```

Persists normalized source/medium/campaign/Blink/referrer attribution for product funnels.

## Analytics and service health

```
GET /api/v1/analytics/product
GET /api/v1/health/services
```

Product analytics are derived from authoritative business data/events. Operational provider/service health is separate.

## Ledgers

```
GET /api/v1/ledgers/activity
GET /api/v1/ledgers/financial
GET /api/v1/ledgers/rewards
GET /api/v1/entitlements
```

Ledger endpoints expose durable movements rather than relying on client-calculated balances.

## Outbox publisher boundary

Protected internal publisher routes:

```
GET  /api/v1/internal/events/outbox
POST /api/v1/internal/events/outbox/:id/published
```

Events contain type, schema version, aggregate ID/version, occurrence time and payload. Consumer inbox deduplication makes replay safe.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sonic-ai-works.gitbook.io/sonic-networks-docs/api-reference/architecture-v2.1-apis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.