How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Futureverse Quests API

Quest detail, public quest discovery, and point allocation.

Futureverse Quests API is one of 6 APIs that Futureverse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Quests. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2025-08-16.

Requests are made against a single base URL, {baseUrl}.

3 operations 2 paths 5 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2025-08-16
Base URL
https://ar-api.futureverse.app/graphql
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Futureverse Quests API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (questApiKey). By default, every request must be authenticated.

  • questApiKey — Quest API key. Must start with the prefix sk and be associated with the quest owner account. Issued on Quest application approval; never expose it in client-si…

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

quests 3

Quest detail, public quest discovery, and point allocation.

GET
/quests
Get public quests
listPublicQuests 1 param → 200400
GET
/quests/{questId}
Get quest details
getQuest 3 params → 200400401404
POST
/quests/{questId}
Allocate quest points
allocateQuestPoints 1 param body → 200400401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are QuestDetail (9 properties), PublicQuest (8 properties), Payout (4 properties), AllocatePointsRequest (2 properties). Each schema is shown below with its type and property counts.

QuestDetail
object
9 properties
Payout
object
4 properties
AllocatePointsResponse
object
1 property
AllocatePointsRequest
object
2 properties 2 required
PublicQuest
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

futureverse-quests-api-openapi.yml Raw ↑

Other APIs Futureverse publishes across the network.

Futureverse Asset Register API
FuturePass Identity (OpenID Connect)
The Root Network Node RPC
The Root Network Documentation MCP Server
Futureverse Campaigns API
Where this information came from

This is an independent, third-party profile of Futureverse Quests API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.