Black Relay
MENU
Public APIRegistryDeveloper docs

Black Relay

Black Relay is a public EVE Frontier API and Registry.

It normalises public Sui events, World API metadata and static client data into searchable, source-labelled records for builders and player tools.

Search RegistryRead DocsView APIStatus
01 //

Current state

APIpublic read-only
Registrypublic explorer
Docspublic
EnvironmentStillness
Cycle6
Indexeractive
Static client dataimported
Data freshnessmixed
Known gapspatch-sensitive names/types

Black Relay indexes public or source-labelled data only. It is a read layer, not transaction authority. Frontier data can change after patches or cycle resets, so check source, cycle and timestamp before relying on a record.

02 //

Live surfaces

01 //

REGISTRY

Public explorer for entities, systems, items, killmails, structures and source evidence.

STATE
CHECKING
02 //

API

Public endpoints for tools, integrations and Black Relay applications.

STATE
CHECKING
03 //

Try the API

These are real public endpoints. They return source-labelled Registry exports from Cloudflare and should be treated as read-side data.

Read API docs
  • GET /v1/health
  • GET /v1/entities
  • GET /v1/events
  • GET /v1/types/:id
  • GET /v1/sources
  • GET /v1/ops/freshness
04 //

Data rules

Source stays attached

Every published record should point back to where it came from.

Confidence is visible

Verified, probable, reported, stale and unknown stay visually distinct.

Current cycle comes first

Cycle 6 Stillness records are the default public view.

Private intel is out of scope

Black Relay does not publish private Discord intel, wallet secrets or unverifiable alt accusations.

Direct reads before transactions

Re-read live Frontier and Sui state before signing, sponsoring, deploying or mutating anything.

05 //

Current scope

Covered data

  • entities, systems, items, events and killmails
  • structures, sources, facts and relations
  • public API and Registry explorer
  • developer documentation
  • source, confidence and freshness labels
  • public exports and operational status

Known gaps

  • some source windows can be stale while upstream indexers catch up
  • static client names and type metadata are patch-sensitive
  • coverage is incomplete where public sources do not expose enough context
  • the API is not transaction authority
06 //

Mission

The frontier speaks in broken signals. Black Relay records public EVE Frontier data from Sui events, World API metadata and static client data, then keeps source, confidence and freshness attached so builders can see what was checked, what is stale and what needs another read. The Registry is the public record, the API is the read layer and the status page shows whether the signal is current. Black Relay does not claim to see the whole frontier; it records what can be checked before rumour hardens into fact.

07 //

Public endpoints

blackrelay.networkHome
├─api.blackrelay.networkPublic API├─registry.blackrelay.networkRegistry explorer├─docs.blackrelay.networkDeveloper docs└─status.blackrelay.networkHealth and freshness
08 //

Join / contribute

Black Relay is maintained by Hēi and Black Relay contributors.

Join Discord for project updates or use GitHub to review source, report data issues and contribute fixes. Our referral link is available here but it is not the project front door.

Discord

Join Discord

Registry updates, source reports and early API discussion.

Join Discord
GitHub

Contribute on GitHub

Public repositories for Black Relay tooling and infrastructure.

Open GitHub