Supported APIs

Molthood's integrations are organised by capability rather than by supplier. A capability is a thing that can be done — read a page, search the web, screen a contract — and more than one source may be able to do it.

Capabilities

Chain state

Balances, blocks, transactions, gas, contract source and verification status.

Market data

Price, liquidity, volume, pool composition and holder distribution.

Security screening

Contract powers: mint authority, pause switches, transfer restrictions, ownership.

Web search

Finding what has been published about a subject.

Page retrieval

Reading a page, including ones that need a browser to render.

Site mapping

Discovering a site's structure before deciding what is worth reading.

Domain records

Registration, certificates, mail posture and archive history.

Code execution

Running analysis over collected data in an isolated sandbox.

Summarisation

Turning findings into prose, after the findings exist.

Missing a capability

The platform is fully functional with zero credentials configured. It starts, it serves, and it routes around whatever is absent. Adding a credential and restarting is the only enablement step — there is no code path that a new one switches on.

Where several sources serve one capability, losing one loses that source and not the run. Where only one does, the capability becomes unavailable and every finding that depended on it becomes an explicit unknown.

Availability is a state with distinct values, not a boolean: a missing credential is a deployment task, a rate limit clears by itself, and an outage is somebody else's problem. Collapsing them would repeat exactly the mistake the evidence model exists to prevent.