Fractal
Fractal is a company surfaced via the API Evangelist harvest backlog (source: vc-portfolio; backed by multicoin-capital, paradigm) and added to the network as a stub for full-pipeline profiling.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Fractal the way a machine reads it — 24 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Fractal scores 30.9/100 (thin), with a separate agent-readiness read of 23/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-31 · rubric v0.25.0
Put this on your own site. The badge is drawn live from Fractal's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fractal-is/"
title="Fractal on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fractal-is.svg"
alt="Fractal Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/fractal-is/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fractal-is/"
title="Fractal on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fractal-is/card.svg"
alt="Fractal Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Fractal
Each block below is one kind of artifact we hold for Fractal. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Fractal Approval Service API
The ApprovalService API from Fractal — 2 operation(s) for approvalservice.
Fractal Chain Service API
The ChainService API from Fractal — 3 operation(s) for chainservice.
Fractal EVM Experimental Service API
The EVMExperimentalService API from Fractal — 5 operation(s) for evmexperimentalservice.
Fractal File Service API
The FileService API from Fractal — 1 operation(s) for fileservice.
Fractal Inventory Management Service API
The InventoryManagementService API from Fractal — 3 operation(s) for inventorymanagementservice.
Fractal Link Account Service API
The LinkAccountService API from Fractal — 1 operation(s) for linkaccountservice.
Fractal Marketplace Service API
The MarketplaceService API from Fractal — 2 operation(s) for marketplaceservice.
Fractal Metagame Service API
The MetagameService API from Fractal — 1 operation(s) for metagameservice.
Fractal OAuth API
The Oauth API from Fractal — 1 operation(s) for oauth.
Fractal Score Service API
The ScoreService API from Fractal — 3 operation(s) for scoreservice.
Fractal Sign In Service V2 API
The SignInServiceV2 API from Fractal — 3 operation(s) for signinservicev2.
Fractal Solana Admin Service API
The SolanaAdminService API from Fractal — 2 operation(s) for solanaadminservice.
Fractal Solana Marketplace Service API
The SolanaMarketplaceService API from Fractal — 2 operation(s) for solanamarketplaceservice.
Fractal Solana Mint Experimental Service API
The SolanaMintExperimentalService API from Fractal — 3 operation(s) for solanamintexperimentalservice.
Fractal Solana Transaction Service API
The SolanaTransactionService API from Fractal — 4 operation(s) for solanatransactionservice.
Fractal Tournament Service API
The TournamentService API from Fractal — 4 operation(s) for tournamentservice.
Fractal Transaction Service API
The TransactionService API from Fractal — 2 operation(s) for transactionservice.
Fractal Wallet Service API
The WalletService API from Fractal — 3 operation(s) for walletservice.
Fractal Auth Service API
The Auth Service API from Fractal — 1 operation(s) for auth service.
Scroll within the panel for all 19 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Fractal Is Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Fractal API Rules
SPECTRALSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Fractal — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
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
← All providers · Data indexed from github.com/api-evangelist/fractal-is · machine-readable index on apis.io
This is an independent, third-party profile of Fractal, 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.