FlareWatch

FlareWatch provides a dashboard for staking rewards, tax liability, and real‑time yield on the Flare network. It runs validator nodes, offers FTSO data feeds, and aggregates multi‑wallet staking positions, delivering alerts, income projections and tax‑ready records for users. The service includes an agent, MCP API, and developer tools, aiming to give transparent on‑chain analytics and staking management.

FlareWatch is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Staking, Dashboards, Validator, and Tax.

The FlareWatch catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

FlareWatch’s developer surface includes authentication, API reference, documentation, support, changelog, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

31.4/100 thin Agent 37/100 agent ready Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessSelf serve

2 APIs 1 MCP Servers

Company Staking Dashboards Validator Tax DeFi

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 31.4/100 · thin

Contract Quality 4.4 / 21

Developer Ergonomics 6.9 / 17

Access Clarity 2.9 / 17

Operational Transparency 2.6 / 11

Contract Governance 2.2 / 10

Discoverability 5.7 / 9

Regulatory Posture 4.6 / 15

Agent readiness — 37/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/flarewatch-io/"><img src="https://apis.io/badge/flarewatch-io/card.svg" alt="FlareWatch on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 20.9 — up to +19.8 composite points Ask about this →
Access Clarity scores 17.0 — up to +16.6 composite points Ask about this →
Developer Ergonomics scores 40.5 — up to +11.9 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

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 the provider profile at artifacts.apis.io/flarewatch-io/apis.yml: open an issue on github.com/api-evangelist/flarewatch-io to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

APIs 2

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

FlareWatch Public API

Read-only REST access to FlareWatch's analytics (validator scores, FTSO metrics, network stats, prices). No API key required.

FlareWatch API

FlareWatch API as documented publicly: 10 operations. Contract generated from the documentation by API Evangelist (2026-11-08); not the provider's own document.

MCP Servers 1

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

FlareWatch MCP Server

Remote MCP server at www.flarewatch.io.

MCP SERVER

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Flarewatch Io Context

4 classes · 25 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

FlareWatch API Rules

37 rules · 35 error-severity 1 warn-severity 1 info-severity

SPECTRAL

JSON Schema 4

Standalone JSON Schema definitions for this provider's data models.

GetApiPaidTaxReconciliationResponse

2 properties

JSON SCHEMA

GetApiPaidWalletIntelligenceResponse

9 properties

JSON SCHEMA

PostApiPayVerifyRequest

8 properties

JSON SCHEMA

PostApiPayVerifyResponse

7 properties

JSON SCHEMA

Security Posture 3

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

FlareWatch Authentication

1 scheme

SECURITY

FlareWatch Domain Security

TLSv1.3 · HSTS · DNSSEC

SECURITY

FlareWatch Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Documentation 2

Reference material describing how the API behaves

APIReference

APIReference

Documentation

Documentation

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

MCPServer

MCPServer

WellKnown

WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conformance

Build 2

SDKs, sample code, and the tooling you integrate with

SDKs

SDKs

Packages

Packages

Access & Security 6

Authentication, authorization, and security posture

Security

Authentication

SecurityTxt

SecurityTxt

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: flarewatch-io
name: FlareWatch
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://www.flarewatch.io/og-image.png
description: FlareWatch provides a dashboard for staking rewards, tax liability, and real‑time yield on the Flare network.
  It runs validator nodes, offers FTSO data feeds, and aggregates multi‑wallet staking positions, delivering alerts, income
  projections and tax‑ready records for users. The service includes an agent, MCP API, and developer tools, aiming to give
  transparent on‑chain analytics and staking management.
url: https://artifacts.apis.io/flarewatch-io/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-08 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-11-08'
modified: '2026-11-08'
tags:
- Company
- Staking
- Dashboards
- Validator
- Tax
- DeFi
tags_raw:
- Company
- Staking
- Dashboard
- Validator
- Tax
- DeFi
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Spectral
  url: rules/flarewatch-io-rules.yml
- type: JSONLD
  url: json-ld/flarewatch-io-context.jsonld
- type: Vocabulary
  url: vocabulary/flarewatch-io-vocabulary.yml
- type: DataModel
  url: data-model/flarewatch-io-data-model.yml
- type: Security
  url: https://www.flarewatch.io/docs/security
- type: Authentication
  url: authentication/flarewatch-io-authentication.yml
- type: Conformance
  url: conformance/flarewatch-io-conformance.yml
- type: LLMsTxt
  url: llms/flarewatch-io-llms.txt
- type: MCPServer
  url: mcp/flarewatch-io-mcp.yml
- type: SecurityTxt
  url: well-known/flarewatch-io-security.txt
- type: SecurityTxt
  url: well-known/flarewatch-io-flarewatch-security.txt
- type: WellKnown
  url: well-known/flarewatch-io-well-known.yml
- type: Hosts
  url: hosts/flarewatch-io-hosts.yml
- type: Vendors
  url: vendors/flarewatch-io-vendors.yml
- type: SDKs
  url: packages/flarewatch-io-packages.yml
- type: Packages
  url: packages/flarewatch-io-packages.yml
- type: APIReference
  url: https://www.flarewatch.io/llms.txt
- type: VulnerabilityDisclosure
  url: security/flarewatch-io-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/flarewatch-io-domain-security.yml
- type: Website
  url: https://flarewatch.io/
- type: Documentation
  url: https://www.flarewatch.io/en/docs/install
- type: Support
  url: https://www.flarewatch.io/en/help
- type: PrivacyPolicy
  url: https://www.flarewatch.io/en/privacy
- type: TermsOfService
  url: https://www.flarewatch.io/disclaimer
- type: ChangeLog
  url: https://www.flarewatch.io/en/changelog
apis:
- name: FlareWatch Public API
  description: Read-only REST access to FlareWatch's analytics (validator scores, FTSO metrics, network stats, prices). No
    API key required.
  humanURL: https://www.flarewatch.io/en/docs/install
  baseURL: https://www.flarewatch.io
  aid: flarewatch-io:flarewatch-public-api
- aid: flarewatch-io:flarewatch-io-api
  name: FlareWatch API
  description: 'FlareWatch API as documented publicly: 10 operations. Contract generated from the documentation by API Evangelist
    (2026-11-08);

    not the provider''s own document.'
  humanURL: https://www.flarewatch.io/developers
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/flarewatch-io-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/flarewatch-io-post-api-pay-verify-request-schema.json
  - type: JSONSchema
    url: json-schema/flarewatch-io-get-api-paid-tax-reconciliation-response-schema.json
  - type: JSONSchema
    url: json-schema/flarewatch-io-get-api-paid-wallet-intelligence-response-schema.json
  - type: JSONSchema
    url: json-schema/flarewatch-io-post-api-pay-verify-response-schema.json
x-enrichment:
  date: '2026-11-08'
  status: enriched
  artifacts_added: 29
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

FlareWatch API — frequently asked questions

Does FlareWatch have an API?

Yes. APIs.io lists 2 APIs from FlareWatch, including FlareWatch Public API and FlareWatch API.

Is there an OpenAPI specification for the FlareWatch API?

Yes. APIs.io indexes 1 OpenAPI specification for FlareWatch, each linked for download from this page.

How do I authenticate with the FlareWatch API?

FlareWatch documents its authentication (1 scheme). The details are profiled on APIs.io as FlareWatch Authentication.

Does FlareWatch have an MCP server?

Yes. APIs.io lists 1 MCP server for FlareWatch: Remote MCP server at www.flarewatch.io.

Is the FlareWatch API ready for AI agents?

FlareWatch has a Kin Score of 31.4 out of 100 (thin) and an Agent Readiness score of 36.5 (agent-ready), scored by API Evangelist on 2026-11-13.

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/flarewatch-io"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/flarewatch-io/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/flarewatch-io/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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