Futureverse website screenshot

Futureverse

Futureverse is a New Zealand-founded "open metaverse" technology company that rolled up eleven startups after a US$54M raise in 2023 and built The Root Network (TRN), a Substrate-based layer-1 blockchain with an EVM layer, any-token gas, and native NFT/SFT, DEX and bridge protocols. Its developer surface is three products: the Asset Register, a Relay-compliant GraphQL API for cross-chain asset metadata, schemas and asset-to-asset links; FuturePass, an OpenID Connect identity and smart-wallet provider; and RootRewards, a points/quest REST API for partner applications. Futureverse Corporation was placed in receivership on 2025-09-30 and in liquidation on 2025-12-16. Its corporate website and its original developer documentation host are both offline, but the TRN documentation, the Asset Register GraphQL endpoint, the FuturePass OIDC provider, the mainnet RPC nodes and 35 npm packages remain live and publicly reachable.

Futureverse publishes 2 APIs on the APIs.io network: Campaigns API and Quests API. Tagged areas include Blockchain, Web3, Metaverse, Digital Assets, and NFT.

The Futureverse catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Futureverse’s developer surface includes documentation, getting-started guide, API reference, changelog, authentication, sandbox, support, and 21 more developer resources.

31.3/100 thin ▬ flat Agent 30/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessSelf serve
1 APIs 2 MCP Servers
BlockchainWeb3MetaverseDigital AssetsNFTGraphQLIdentityOpenID Connectasset-registryLayer 1EVMGamingagent-nativeMCP

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/futureverse: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

Futureverse Asset Register API

Relay-compliant GraphQL API for the Asset Register — a metadata ledger that defines what an asset is, what it can do, and which environments it works in, across chains and for o...

FuturePass Identity (OpenID Connect)

FuturePass is Futureverse's smart-wallet identity system, exposed to developers as a standards compliant OpenID Connect provider. The discovery document at login.futureverse.app...

The Root Network Node RPC

Public archive-node RPC for The Root Network mainnet, exposing both the Substrate JSON-RPC surface (author, babe, chain, state, system and custom nft/dex/fee-proxy methods over ...

The Root Network Documentation MCP Server

Remote, unauthenticated Model Context Protocol server on the documentation host exposing three tools — documentation search, a read-only virtual filesystem over the docs corpus,...

Futureverse Campaigns API

Public campaign detail. Campaigns group quests but hold no balances.

Futureverse Quests API

Quest detail, public quest discovery, and point allocation.

MCP Servers 2

Model Context Protocol servers that expose these APIs to AI agents.

The Root Network

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Futureverse Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Futureverse Authentication

openIdConnect/oauth2/apiKey/http · 6 schemes

SECURITY

Futureverse Domain Security

TLSv1.3 · HSTS

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Futureverse Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: futureverse
name: Futureverse
description: 'Futureverse is a New Zealand-founded "open metaverse" technology company that rolled up eleven startups after
  a US$54M raise in 2023 and built The Root Network (TRN), a Substrate-based layer-1 blockchain with an EVM layer, any-token
  gas, and native NFT/SFT, DEX and bridge protocols. Its developer surface is three products: the Asset Register, a Relay-compliant
  GraphQL API for cross-chain asset metadata, schemas and asset-to-asset links; FuturePass, an OpenID Connect identity and
  smart-wallet provider; and RootRewards, a points/quest REST API for partner applications. Futureverse Corporation was placed
  in receivership on 2025-09-30 and in liquidation on 2025-12-16. Its corporate website and its original developer documentation
  host are both offline, but the TRN documentation, the Asset Register GraphQL endpoint, the FuturePass OIDC provider, the
  mainnet RPC nodes and 35 npm packages remain live and publicly reachable.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-09-02'
  method: derived
image: https://mintlify.s3.us-west-1.amazonaws.com/therootnetwork/images/trn-hero.png
url: https://raw.githubusercontent.com/api-evangelist/futureverse/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-16'
modified: '2026-08-16'
tags:
- Blockchain
- Web3
- Metaverse
- Digital Assets
- NFT
- GraphQL
- Identity
- OpenID Connect
- asset-registry
- Layer 1
- EVM
- Gaming
- agent-native
- MCP
tags_raw:
- blockchain
- web3
- metaverse
- digital-assets
- nft
- graphql
- identity
- openid-connect
- asset-registry
- layer-1
- evm
- gaming
- agent-native
- mcp
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Futureverse Asset Register API
  description: Relay-compliant GraphQL API for the Asset Register — a metadata ledger that defines what an asset is, what
    it can do, and which environments it works in, across chains and for off-chain assets. 29 queries cover assets, asset
    trees, collections, token schemas, namespaces, accounts, owners, transactions and webhook subscriptions; 28 mutations
    cover schema registration, asset linking, off-chain asset registration, profiles and webhook management. Introspection
    is open and anonymous; writes require a Sign-In-With-Ethereum bearer token or a wallet-signed ARTM transaction.
  humanURL: https://docs.therootnetwork.com/asset-register/introduction
  baseURL: https://ar-api.futureverse.app/graphql
  tags:
  - GraphQL
  - Digital Assets
  - asset-registry
  - NFT
  - Web3
  - Blockchain
  tags_raw:
  - graphql
  - digital-assets
  - asset-registry
  - nft
  - web3
  - blockchain
  properties:
  - type: GraphQL
    url: https://ar-api.futureverse.app/graphql
  - type: GraphQL
    url: graphql/futureverse-asset-register.graphql
  - type: Documentation
    url: https://docs.therootnetwork.com/asset-register/introduction
  - type: APIReference
    url: https://docs.therootnetwork.com/asset-register/getting-started
  - type: GettingStarted
    url: https://docs.therootnetwork.com/asset-register/getting-started
  - type: DeveloperPortal
    url: https://ar-docs.futureverse.app/
  - type: Authentication
    url: authentication/futureverse-authentication.yml
  - type: Conventions
    url: conventions/futureverse-conventions.yml
  - type: DataModel
    url: data-model/futureverse-data-model.yml
  - type: ErrorCatalog
    url: errors/futureverse-problem-types.yml
  - type: Webhooks
    url: asyncapi/futureverse-asset-register-events.yml
  - type: Sandbox
    url: sandbox/futureverse-sandbox.yml
- name: FuturePass Identity (OpenID Connect)
  description: FuturePass is Futureverse's smart-wallet identity system, exposed to developers as a standards compliant OpenID
    Connect provider. The discovery document at login.futureverse.app advertises authorization, token, userinfo, introspection,
    revocation, end-session and pushed authorization request endpoints, PKCE S256, five client authentication methods, and
    custom claims that bind an OIDC subject to an EOA, a custodian, a chain ID and a FuturePass address.
  humanURL: https://docs.therootnetwork.com/learn/features/identity-protocol
  baseURL: https://login.futureverse.app
  tags:
  - Identity
  - OpenID Connect
  - Authentication
  - Web3
  tags_raw:
  - identity
  - openid-connect
  - oauth
  - authentication
  - web3
  properties:
  - type: OpenIDConnect
    url: https://login.futureverse.app/.well-known/openid-configuration
  - type: WellKnown
    url: well-known/futureverse-openid-configuration.json
  - type: OAuthScopes
    url: scopes/futureverse-scopes.yml
  - type: Authentication
    url: authentication/futureverse-authentication.yml
  - type: Documentation
    url: https://docs.therootnetwork.com/learn/features/identity-protocol
- name: The Root Network Node RPC
  description: Public archive-node RPC for The Root Network mainnet, exposing both the Substrate JSON-RPC surface (author,
    babe, chain, state, system and custom nft/dex/fee-proxy methods over HTTP and WebSocket) and an Ethereum-compatible EVM
    JSON-RPC on chain ID 7668. The documentation warns these public endpoints are "not for sustained or business use".
  humanURL: https://docs.therootnetwork.com/build/substrate/api-reference/json-rpc
  baseURL: https://root.rootnet.live/archive
  tags:
  - Blockchain
  - JSON-RPC
  - EVM
  - Layer 1
  - Substrate
  tags_raw:
  - blockchain
  - json-rpc
  - evm
  - layer-1
  - substrate
  properties:
  - type: APIReference
    url: https://docs.therootnetwork.com/build/substrate/api-reference/json-rpc
  - type: Documentation
    url: https://docs.therootnetwork.com/build/connecting-to-the-root-network
  - type: Sandbox
    url: sandbox/futureverse-sandbox.yml
  - type: Lifecycle
    url: lifecycle/futureverse-lifecycle.yml
- name: The Root Network Documentation MCP Server
  description: Remote, unauthenticated Model Context Protocol server on the documentation host exposing three tools — documentation
    search, a read-only virtual filesystem over the docs corpus, and a feedback submitter. It is a documentation agent surface
    only; it cannot call the Asset Register, FuturePass or RootRewards APIs.
  humanURL: https://docs.therootnetwork.com/intro
  baseURL: https://docs.therootnetwork.com/mcp
  tags:
  - MCP
  - agent-native
  - Documentation
  tags_raw:
  - mcp
  - agent-native
  - documentation
  properties:
  - type: MCPServer
    url: https://docs.therootnetwork.com/mcp
  - type: MCPServer
    url: mcp/futureverse-mcp.yml
  - type: ToolCrosswalk
    url: mcp/futureverse-tool-crosswalk.yml
  - type: AgentCard
    url: a2a/futureverse-a2a.yml
  - type: LLMsTxt
    url: llms/futureverse-llms.txt
- aid: futureverse:futureverse-campaigns-api
  name: Futureverse Campaigns API
  description: Public campaign detail. Campaigns group quests but hold no balances.
  humanURL: https://docs.therootnetwork.com/asset-register/introduction
  baseURL: https://ar-api.futureverse.app/graphql
  tags:
  - Campaigns
  tags_raw:
  - campaigns
  properties:
  - type: OpenAPI
    url: openapi/futureverse-campaigns-api-openapi.yml
  - type: Documentation
    url: https://docs.therootnetwork.com/rootrewards/overview
  - type: APIReference
    url: https://docs.therootnetwork.com/rootrewards/api-reference
  - type: Sandbox
    url: https://docs.therootnetwork.com/rootrewards/testing-instructions
  - type: ErrorCatalog
    url: errors/futureverse-problem-types.yml
- aid: futureverse:futureverse-quests-api
  name: Futureverse Quests API
  description: Quest detail, public quest discovery, and point allocation.
  humanURL: https://docs.therootnetwork.com/asset-register/introduction
  baseURL: https://ar-api.futureverse.app/graphql
  tags:
  - Quests
  tags_raw:
  - quests
  properties:
  - type: OpenAPI
    url: openapi/futureverse-quests-api-openapi.yml
  - type: Documentation
    url: https://docs.therootnetwork.com/rootrewards/overview
  - type: APIReference
    url: https://docs.therootnetwork.com/rootrewards/api-reference
  - type: Sandbox
    url: https://docs.therootnetwork.com/rootrewards/testing-instructions
  - type: ErrorCatalog
    url: errors/futureverse-problem-types.yml
common:
- type: Website
  url: https://www.futureverse.com/
- type: DeveloperPortal
  url: https://docs.therootnetwork.com/intro
- type: Documentation
  url: https://docs.therootnetwork.com/intro
- type: GettingStarted
  url: https://docs.therootnetwork.com/build/getting-started
- type: APIReference
  url: https://docs.therootnetwork.com/build/substrate/api-reference/json-rpc
- type: ChangeLog
  url: https://docs.therootnetwork.com/changelog
- type: ChangeLog
  url: changelog/futureverse-changelog.yml
- type: LLMsTxt
  url: llms/futureverse-llms.txt
- type: AgentCard
  url: a2a/futureverse-a2a.yml
- type: WellKnown
  url: well-known/futureverse-well-known.yml
- type: Packages
  url: packages/futureverse-packages.yml
- type: SDKs
  url: packages/futureverse-packages.yml
- type: Components
  url: components/futureverse-components.yml
- type: Authentication
  url: authentication/futureverse-authentication.yml
- type: OAuthScopes
  url: scopes/futureverse-scopes.yml
- type: Conventions
  url: conventions/futureverse-conventions.yml
- type: Conformance
  url: conformance/futureverse-conformance.yml
- type: ErrorCatalog
  url: errors/futureverse-problem-types.yml
- type: Lifecycle
  url: lifecycle/futureverse-lifecycle.yml
- type: DataModel
  url: data-model/futureverse-data-model.yml
- type: Webhooks
  url: asyncapi/futureverse-asset-register-events.yml
- type: Sandbox
  url: sandbox/futureverse-sandbox.yml
- type: Plans
  url: plans/futureverse-plans-pricing.yml
- type: RateLimits
  url: rate-limits/futureverse-rate-limits.yml
- type: DomainSecurity
  url: security/futureverse-domain-security.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Support
  url: https://discord.gg/TheRootNetwork
- type: Listing
  url: https://www.hiive.com/securities/futureverse-stock
x-enrichment:
  date: '2026-08-16'
  status: enriched
  artifacts_added: 30
  pass: local-v1
x-base-url-reconciliation:
  tool: 0-working/repair-api-bases.py
  verdict: disagreement
  resolution: Not a defect. The four hosts belong to four different products and each was assigned from the provider's own
    documentation — ar-api.futureverse.app for the Asset Register (named in the Asset Register getting-started page), login.futureverse.app
    for FuturePass (the OIDC issuer in its own discovery document), root.rootnet.live/archive for the mainnet node (named
    on the connecting-to-The-Root-Network page), and docs.therootnetwork.com/mcp for the documentation MCP server (probed
    live). Nothing was picked for all of them. The RootRewards Quest API is left WITHOUT a baseURL because Futureverse does
    not publish one.
x-pointers-deliberately-absent:
- type: Deprecation
  reason: No deprecation or sunset policy is published and no RFC 8594 headers are documented. The only deprecation evidence
    is after-the-fact runtime changelog notes. Emitting the pointer would assert a policy Futureverse does not have.
- type: StatusPage
  reason: status.futureverse.com and status.therootnetwork.com do not resolve. futureverse.statuspage.io and therootnetwork.statuspage.io
    both return 200, but so does a nonsense control subdomain — every *.statuspage.io host redirects to Atlassian marketing.
    Recorded as a false positive in lifecycle/futureverse-lifecycle.yml.
- type: Security
  reason: probe-security-programs.py found no security.txt, no bug bounty and no disclosure page on any host (vdp=none). /.well-known/security.txt
    is 404 or 403 everywhere.
- type: Compliance
  reason: No trust center and no named certification (SOC 2, ISO 27001, PCI, HIPAA, FedRAMP) is published anywhere (trust=none).
- type: Idempotency
  reason: No idempotency key on any surface. Per-address ARTM nonces prevent replay but do not make a client retry safe, and
    RootRewards point allocation has no duplicate protection at all. See conventions/futureverse-conventions.yml.
- type: AsyncAPI
  reason: A real webhook surface exists and is catalogued, but no AsyncAPI document is published (/asyncapi.yaml and /asyncapi.json
    both 404). Only the Webhooks pointer is emitted.
- type: GitHubOrganization
  reason: github.com/futureversecom, github.com/therootnetwork and github.com/futureverseai all return 404. github.com/futureverse
    is a DIFFERENT entity — the R parallelization framework.
- type: Blog
  reason: https://www.therootnetwork.com/blog returns 404; the Webflow site was removed.
- type: Pricing
  reason: No pricing page exists on any reachable surface. See plans/futureverse-plans-pricing.yml (plan_count 0).

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/futureverse"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/futureverse/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/futureverse/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.