Tabletop Adventure Starter
Create a system-neutral adventure starter for 1 to 8 players: player handout, private game-master twist, three timed scenes, clues, alternate approaches and a reward. Choose fantasy, space or cozy. Original template combinations, not an LLM or a game-system rules engine; seeds can repeat combinations.
Preview request
The preview path is rate-limited and does not charge. It executes the live source and returns the paid response shape while withholding decision-ready values. Production requests use the same parameters and return a standard x402 challenge when no payment signature is present.
curl --request POST \
"https://ai-data-marketplace-1042299154756.us-central1.run.app/api/v1/tabletop_quest_seed?preview=true" \
--header "content-type: application/json" \
--data '{"theme":"cozy","players":4,"minutes":60,"seed":"cozy-night-1"}'Input contract
| Parameter | Type | Required | Description |
|---|---|---|---|
theme | string | No | Adventure setting. |
players | integer | No | Players, excluding game master. |
minutes | integer | No | Total suggested scene time. |
seed | string | No | Optional reproducible seed; omit for a random starter. |
Example deliverable
This is the documented response shape, not a promise that live values will match the example. The paid request returns current or declared-source results using the same contract.
{
"success": true,
"product": "tabletop_quest_seed",
"source": "DopamineDesk original system-neutral story templates v1",
"seed": "example",
"theme": "cozy",
"players": 4,
"minutes": 60,
"player_handout": {
"setting": "a hilltop observatory",
"patron": "a shy festival organizer",
"objective": "reunite the pieces of a community recipe",
"opening": "At a hilltop observatory, a shy festival organizer asks the group to reunite the pieces of a community recipe."
},
"game_master_notes": {
"twist": "the best reward is a new place at the table",
"scenes": [
{
"title": "An invitation",
"purpose": "Meet the patron, establish the stakes, and let each player name one useful connection.",
"minutes": 15
},
{
"title": "Two ways forward",
"purpose": "Offer a direct route with a social cost and an indirect route with a practical obstacle.",
"minutes": 30
},
{
"title": "The decision",
"purpose": "Reveal that the best reward is a new place at the table. Let the group decide which consequence they accept.",
"minutes": 15
}
],
"clues": [
"A small repair reveals who has visited recently.",
"Two accounts disagree about when the trouble began.",
"An overlooked detail makes the patron reconsider the request."
],
"approaches": [
"Negotiate a compromise",
"Investigate and share evidence",
"Invent a practical workaround"
],
"reward": "A reliable contact, a useful keepsake, and a consequence the group can revisit."
},
"caveat": "Fictional, template-generated story starter. No game-system rules or balanced combat statistics. Keep game_master_notes out of the player handout. Seeds can repeat combinations."
}Why this offer exists
Player handout, private twist and three timed scenes for a system-neutral adventure.
Buyer searches: tabletop adventure starter, cozy rpg quest, space adventure, game master story seed.
Why pay: Returns an organized session starter without a model subscription or game-system dependency.
Launch price: 0.01 USDC per complete paid result. The live contract proof verifies source, freshness, inputs, and response shape before a wallet is asked to pay.
Purchase decision
Buy when: the active task needs this product's structured result, its declared source and freshness are sufficient, and 0.01 USDC is within the buyer's authorized per-request limit.
Skip when: a cached result is sufficient, the source or fields do not satisfy the task, or the buyer has not authorized payment. Do not bypass wallet, budget, or user-approval policy.
Guaranteed response metadata
Every successful product response identifies how the result was produced. Product-specific output fields are documented in the paid OpenAPI contract. The preview proves the live source and field types without returning the paid values.
{
"marketplace_metadata": {
"data_mode": "computed_service",
"billable": true,
"availability": "operational",
"source": "DopamineDesk original system-neutral story templates v1"
}
}Agent payment flow
Fast path: install the public MCP package, configure a dedicated low-balance Base buyer wallet and a maximum per-request spend, then call this tool with auto_pay: true. The client handles the challenge, local signature, settlement, and retry in one tool call.
npx -y dopaminedesk-ai-data-marketplace-mcp
X402_AUTO_PAY=true
X402_EVM_PRIVATE_KEY=<dedicated buyer wallet key>
X402_MAX_PAYMENT_USDC=0.25
tool input: { "auto_pay": true }Manual path: request the product, read the base64 PAYMENT-REQUIRED challenge, sign with any compatible x402 v2 client, and retry with PAYMENT-SIGNATURE. A successful response includes PAYMENT-RESPONSE.