Overview
NASDUCK is infrastructure for a player-driven memecoin economy inside GTA VI. Everything a player does in the in-game overlay is also open to builders through four surfaces: overlay hooks, the event bus, the indexer and webhooks.
All of it is implemented in the open. The engine, the bindings, the schemas and the reference for every surface live in the repository and are versioned with it. Nothing here is a black box, and nothing here is duplicated on this page.
Requests go to https://api.nasduck.org/v1 with a bearer key. Keys are issued per account in the overlay under Settings, then Builders; the header format and the key lifecycle are written out in the reference.
Tokens are Solana SPL tokens. Amounts are in base units unless a field name ends in Ui. Fees are paid in SOL.
Getting started
Installation paths for the CLI and for all four language bindings are in the README. The client is one typed surface over the indexer, the event bus and webhook verification, with no runtime dependencies, and it works in Node and in the browser.
Start with a read: a single token lookup confirms your key and base URL. Reference implementations for every surface sit under bindings, and the engine contract under references.
Getting startedScene Launch
A Scene Launch turns the frame under the reticle into a token. The capture is stored with its place and time and stays attached to the token as its origin.
A launch moves through five states: aiming, captured, named, confirmed, launched. Nothing is stored while aiming; pressing square holds the frame for thirty days; naming sets the ticker; confirming approves the mint fee; launching creates the SPL mint and lists the token. The capture stays readable for the whole retention window, including after the token goes live.
Scene LaunchOverlay hooks
Hooks are small functions the overlay calls at fixed points in a launch: on capture, on naming, on confirmation and on completion. They run in the order they were registered and may only return what the hook is documented to change. A hook that throws is skipped and the launch continues.
Hooks run on the player's machine, so the budget is tight. The reference states it.
Overlay hooksEvent bus
One ordered stream. Every event carries a type, a sequence number and a payload: token launches, migrations, graduations and filled trades. Because sequence numbers are monotonic per stream, a reconnecting client resumes from the last number it stored and nothing is skipped.
Event busSDK
The client covers the indexer, the event bus and webhook verification in one typed interface, generated from the same schema as the engine. A field that exists in the repository exists in the client, and the types ship with the package. There is no separate types install.
SDKIndexer
Read-only HTTP and JSON over tokens, single tokens, per-token trades, captures and search. Lists are paged with a cursor: the previous response carries the cursor for the next page, and cursors expire after ten minutes.
Response shapes are pinned by fixtures in crates, so a change to the wire format is visible in review.
IndexerWebhooks
The same events as the bus, delivered to an HTTPS endpoint you control. Every delivery is signed, and the signature must be checked against the raw body before any parsing. An endpoint that answers 2xx within five seconds is done; anything else is retried with backoff for twenty-four hours, and a 410 drops the delivery without retry.
The verification helper and the header name are in the reference.
WebhooksRate limits
Limits are per key, not per account, and reset on a fixed minute boundary. Reads and writes are budgeted separately; the event bus is not counted against either.
Rate limitsErrors
Every error carries a stable code and, where retrying helps, a number of seconds to wait. Codes do not change; message text does. The full table and the retry semantics are in the reference.
ErrorsWhere things live
Engine and bindings CLI contract Install paths Breakage reports
