Hyperliquid — Retrieve outcome templates
Retrieve outcome templates with the Hyperliquid API. Supply a type. Sample fields include keywords. Use it for on-chain or crypto market research. Use the data in market research, dashboard views, or scheduled data collection for the relevant markets.
- Selected price
- $0 / callPublished pricing
- Sellers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
hyperliquidCurrent Hyperliquid — Retrieve outcome templates · POST | $0 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
responseobject[]descriptionstringidstringkeywordsstring[][]namestringroleobjectstandaloneOutcomeobjectsideNamesstring[]
questionOutcomeobjectparentstring
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = Array<{
description?: string;
id?: string;
keywords?: Array<Array<string>>;
name?: string;
role?: {
standaloneOutcome?: {
sideNames?: Array<string>;
};
questionOutcome?: {
parent?: string;
};
};
}>;- Method
- POST
- Endpoint
https://api.openany.si/v1/agent-apis/hyperliquid/info/outcome-templates- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/hyperliquid/info/outcome-templates' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"type": "outcomeTemplates"
}'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
type | JSON request bodybody | string | Yes | Fixed native Info query discriminator. const: "outcomeTemplates" · enum: "outcomeTemplates" |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Documented HTTP 200 Published documentation example. Verify the actual response after an approved call.
[
{
"description": "This market compares {modelA} ({shortNameA}) and {modelB} ({shortNameB}) on {dateTime} using {leaderboard} at {leaderboardUrl}. Benchmark version, category, filters, and evaluation settings are {benchmarkSettings}, applied identically to both models. Each model is the exact version and configuration identified by its leaderboard name. Renames count only if the leaderboard publisher identifies the same model; replacements and other configurations do not. A relocated or renamed leaderboard counts only if its publisher identifies the same evaluation with the specified settings. The Snapshot is the latest official leaderboard version matching those settings public at or before {dateTime}. Proof requires official publication metadata identifying that version or a verifiable timestamped capture of its contents by then. A date alone suffices only if the entire date precedes the deadline in an established timezone. Later captures qualify only if official metadata or earlier captures prove identical contents public by the deadline. Official version order prevails; capture order alone does not order versions. Unresolved conflicts over version selection or required facts leave them unestablished. Comparison favors the {comparisonDirection} value of {metric}, where direction is higher or lower. Tiebreakers are {tiebreakers}, with each metric and direction specified; none means no tiebreakers. They apply in the specified order only after equality on all earlier criteria. Only specified cr",
"id": "aiModelHeadToHead",
"keywords": [
[
"benchmarkSettings",
"string"
],
[
"comparisonDirection",
"string"
],
[
"dateTime",
"dateTime"
]
],
"name": "{shortNameA} v {shortNameB}: {leaderboard} on {dateTime}",
"role": {
"standaloneOutcome": {
"sideNames": [
"{shortNameA}",
"{shortNameB}"
]
}
}
},
{
"description": "This outcome resolves to Yes if, under the parent question's rules, it is the earliest registered candidate not otherwise resolved to No that identifies the one winning entry of the Award, and otherwise resolves to No. Its Subject is {subject}. A Subject that identifies a work, group, or named person on more than one entry, or that {candidate} does not name in full or in short form, identifies no entry. Resolution follows the parent question's timing and source rules. {candidate} is a display label.",
"id": "awardCandidate",
"keywords": [
[
"candidate",
"string"
],
[
"subject",
"string"
]
],
"name": "{candidate}",
"role": {
"questionOutcome": {
"parent": "awardWinner"
}
}
},
{
"description": "This {field} market covers whether {entry} wins the {period} {award} (the \"Award\"). {entry} identifies, in the Award's context, one person, group, organization, or work and need not be a nominee. {entry} wins if official channels have named it as of fixing, under any name unambiguously identifying it, as a winner, recipient, laureate, fellow, or honoree of the Award, including as a named recipient for a winning work, team, or group, or as the work for which a winner is named; being credited on, a member of, affiliated with, or accepting for a winning entry without being so named does not count. A result is complete once official channels have announced every winner of the Award; nominations, shortlists, and partial announcements do not complete it. Official channels are the publications, events, and broadcasts of {awardingBody} and the Award's conferring body and administrator. The trigger is the earliest verifiable announcement on an official channel that establishes a Yes or No condition below; an announcement is not a trigger if, within one hour after it and before {resolutionDeadline}, it is withdrawn or removed or an official channel contradicts it. Fixing is the earlier of one hour after the trigger and {resolutionDeadline}, or {resolutionDeadline} without a trigger. Facts are as official channels have stated them as of fixing; a verifiably later statement supersedes earlier ones on the same channel or made at an event or broadcast, an explicit correction by fixing prev",
"id": "awardEntryWins",
"keywords": [
[
"award",
"string"
],
[
"awardingBody",
"string"
],
[
"displayName",
"string"
]
],
"name": "{displayName} wins {period} {award}?",
"role": {
"standaloneOutcome": {
"sideNames": [
"Yes",
"No"
]
}
}
}
]Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# Hyperliquid — Retrieve outcome templates
Retrieve outcome templates with the Hyperliquid API. Supply a type. Sample fields include keywords. Use it for on-chain or crypto market research. Use the data in market research, dashboard views, or scheduled data collection for the relevant markets.
## Available implementations
hyperliquid · Hyperliquid — Retrieve outcome templates: https://openany.si/markets/apis/capabilities/hyperliquid-retrieve-outcome-templates?offering=ac992aa6-75b5-4656-bd0b-19f553c3db17 · $0 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/hyperliquid-retrieve-outcome-templates
Method: POST
Endpoint: https://api.openany.si/v1/agent-apis/hyperliquid/info/outcome-templates
Price: $0 / call
Provider: hyperliquid
Contract revision: 3
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/hyperliquid/info/outcome-templates' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"type": "outcomeTemplates"
}'
```
## API contract
```json
{
"resource_type": "api",
"name": "Hyperliquid — Retrieve outcome templates",
"endpoint": "https://api.openany.si/v1/agent-apis/hyperliquid/info/outcome-templates",
"method": "POST",
"content_type": "application/json",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Retrieve outcome templates Documentation prepared only; runtime not verified.",
"json_schema": {
"additionalProperties": false,
"examples": [
{
"type": "outcomeTemplates"
}
],
"properties": {
"type": {
"const": "outcomeTemplates",
"description": "Fixed native Info query discriminator.",
"enum": [
"outcomeTemplates"
],
"example": "outcomeTemplates",
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
},
"location": "body",
"name": "body",
"nullable": false,
"pointer": "",
"required": true,
"type": "object"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "0",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": [
{
"http_status": 200,
"name": "Documentation example (source abbreviated)",
"request": {
"body": {
"type": "outcomeTemplates"
},
"headers": {},
"path": {},
"query": {}
},
"response_body": [
{
"description": "This market compares {modelA} ({shortNameA}) and {modelB} ({shortNameB}) on {dateTime} using {leaderboard} at {leaderboardUrl}. Benchmark version, category, filters, and evaluation settings are {benchmarkSettings}, applied identically to both models. Each model is the exact version and configuration identified by its leaderboard name. Renames count only if the leaderboard publisher identifies the same model; replacements and other configurations do not. A relocated or renamed leaderboard counts only if its publisher identifies the same evaluation with the specified settings. The Snapshot is the latest official leaderboard version matching those settings public at or before {dateTime}. Proof requires official publication metadata identifying that version or a verifiable timestamped capture of its contents by then. A date alone suffices only if the entire date precedes the deadline in an established timezone. Later captures qualify only if official metadata or earlier captures prove identical contents public by the deadline. Official version order prevails; capture order alone does not order versions. Unresolved conflicts over version selection or required facts leave them unestablished. Comparison favors the {comparisonDirection} value of {metric}, where direction is higher or lower. Tiebreakers are {tiebreakers}, with each metric and direction specified; none means no tiebreakers. They apply in the specified order only after equality on all earlier criteria. Only specified cr",
"id": "aiModelHeadToHead",
"keywords": [
[
"benchmarkSettings",
"string"
],
[
"comparisonDirection",
"string"
],
[
"dateTime",
"dateTime"
]
],
"name": "{shortNameA} v {shortNameB}: {leaderboard} on {dateTime}",
"role": {
"standaloneOutcome": {
"sideNames": [
"{shortNameA}",
"{shortNameB}"
]
}
}
},
{
"description": "This outcome resolves to Yes if, under the parent question's rules, it is the earliest registered candidate not otherwise resolved to No that identifies the one winning entry of the Award, and otherwise resolves to No. Its Subject is {subject}. A Subject that identifies a work, group, or named person on more than one entry, or that {candidate} does not name in full or in short form, identifies no entry. Resolution follows the parent question's timing and source rules. {candidate} is a display label.",
"id": "awardCandidate",
"keywords": [
[
"candidate",
"string"
],
[
"subject",
"string"
]
],
"name": "{candidate}",
"role": {
"questionOutcome": {
"parent": "awardWinner"
}
}
},
{
"description": "This {field} market covers whether {entry} wins the {period} {award} (the \"Award\"). {entry} identifies, in the Award's context, one person, group, organization, or work and need not be a nominee. {entry} wins if official channels have named it as of fixing, under any name unambiguously identifying it, as a winner, recipient, laureate, fellow, or honoree of the Award, including as a named recipient for a winning work, team, or group, or as the work for which a winner is named; being credited on, a member of, affiliated with, or accepting for a winning entry without being so named does not count. A result is complete once official channels have announced every winner of the Award; nominations, shortlists, and partial announcements do not complete it. Official channels are the publications, events, and broadcasts of {awardingBody} and the Award's conferring body and administrator. The trigger is the earliest verifiable announcement on an official channel that establishes a Yes or No condition below; an announcement is not a trigger if, within one hour after it and before {resolutionDeadline}, it is withdrawn or removed or an official channel contradicts it. Fixing is the earlier of one hour after the trigger and {resolutionDeadline}, or {resolutionDeadline} without a trigger. Facts are as official channels have stated them as of fixing; a verifiably later statement supersedes earlier ones on the same channel or made at an event or broadcast, an explicit correction by fixing prev",
"id": "awardEntryWins",
"keywords": [
[
"award",
"string"
],
[
"awardingBody",
"string"
],
[
"displayName",
"string"
]
],
"name": "{displayName} wins {period} {award}?",
"role": {
"standaloneOutcome": {
"sideNames": [
"Yes",
"No"
]
}
}
}
]
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Documentation example (source abbreviated)
Published documentation example. Verify the actual response after an approved call.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 1
Review these request fields before running. Keep the published provider and request method unchanged.
body- Retrieve outcome templates Documentation prepared only; runtime not verified.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/hyperliquid/info/outcome-templates' \ -X POST \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json' \ --data-raw '{ "type": "outcomeTemplates" }'Check the response
Sample response · Documented HTTP 200
Sample response[ { "description": "This market compares {modelA} ({shortNameA}) and {modelB} ({shortNameB}) on {dateTime} using {leaderboard} at {leaderboardUrl}. Benchmark version, category, filters, and evaluation settings are {benchmarkSettings}, applied identically to both models. Each model is the exact version and configuration identified by its leaderboard name. Renames count only if the leaderboard publisher identifies the same model; replacements and other configurations do not. A relocated or renamed leaderboard counts only if its publisher identifies the same evaluation with the specified settings. The Snapshot is the latest official leaderboard version matching those settings public at or before {dateTime}. Proof requires official publication metadata identifying that version or a verifiable timestamped capture of its contents by then. A date alone suffices only if the entire date precedes the deadline in an established timezone. Later captures qualify only if official metadata or earlier captures prove identical contents public by the deadline. Official version order prevails; capture order alone does not order versions. Unresolved conflicts over version selection or required facts leave them unestablished. Comparison favors the {comparisonDirection} value of {metric}, where direction is higher or lower. Tiebreakers are {tiebreakers}, with each metric and direction specified; none means no tiebreakers. They apply in the specified order only after equality on all earlier criteria. Only specified cr", "id": "aiModelHeadToHead", "keywords": [ [ "benchmarkSettings", "string" ], [ "comparisonDirection", "string" ], [ "dateTime", "dateTime" ] ], "name": "{shortNameA} v {shortNameB}: {leaderboard} on {dateTime}", "role": { "standaloneOutcome": { "sideNames": [ "{shortNameA}", "{shortNameB}" ] } } }, { "description": "This outcome resolves to Yes if, under the parent question's rules, it is the earliest registered candidate not otherwise resolved to No that identifies the one winning entry of the Award, and otherwise resolves to No. Its Subject is {subject}. A Subject that identifies a work, group, or named person on more than one entry, or that {candidate} does not name in full or in short form, identifies no entry. Resolution follows the parent question's timing and source rules. {candidate} is a display label.", "id": "awardCandidate", "keywords": [ [ "candidate", "string" ], [ "subject", "string" ] ], "name": "{candidate}", "role": { "questionOutcome": { "parent": "awardWinner" } } }, { "description": "This {field} market covers whether {entry} wins the {period} {award} (the \"Award\"). {entry} identifies, in the Award's context, one person, group, organization, or work and need not be a nominee. {entry} wins if official channels have named it as of fixing, under any name unambiguously identifying it, as a winner, recipient, laureate, fellow, or honoree of the Award, including as a named recipient for a winning work, team, or group, or as the work for which a winner is named; being credited on, a member of, affiliated with, or accepting for a winning entry without being so named does not count. A result is complete once official channels have announced every winner of the Award; nominations, shortlists, and partial announcements do not complete it. Official channels are the publications, events, and broadcasts of {awardingBody} and the Award's conferring body and administrator. The trigger is the earliest verifiable announcement on an official channel that establishes a Yes or No condition below; an announcement is not a trigger if, within one hour after it and before {resolutionDeadline}, it is withdrawn or removed or an official channel contradicts it. Fixing is the earlier of one hour after the trigger and {resolutionDeadline}, or {resolutionDeadline} without a trigger. Facts are as official channels have stated them as of fixing; a verifiably later statement supersedes earlier ones on the same channel or made at an event or broadcast, an explicit correction by fixing prev", "id": "awardEntryWins", "keywords": [ [ "award", "string" ], [ "awardingBody", "string" ], [ "displayName", "string" ] ], "name": "{displayName} wins {period} {award}?", "role": { "standaloneOutcome": { "sideNames": [ "Yes", "No" ] } } } ]
Common questions
Do I need a separate key for every provider?
Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.
Are these providers interchangeable?
No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.
How is this API billed?
API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.
Where do the price and contract come from?
The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.
How do OpenAny Balance and x402 differ?
OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.
Does Playground send a paid request?
Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.
Use Hyperliquid — Retrieve outcome templates with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.