FabricBloc APIs are designed around scoped API keys, public service contracts, and static documentation that matches the generated OpenAPI artifacts.
Pick a capability
Start from the capability you need to ship first. Wallets create account infrastructure, tokens create ERC-20 assets, NFTs create collections, and agent integrations let tool-using assistants act through scoped credentials.
Create an API key
Use the FabricBloc console to create a project and issue an API key with only the scopes needed by the workflow. Keep keys out of browser code and rotate them when they leave a trusted environment.
Make the first request
Use the API reference for the service you are integrating. Each generated service page opens the Scalar reference for that API, while the human-written docs explain the workflow around it.
curl -H "Authorization: Bearer $FABRICBLOC_API_KEY" \
https://api.fabricbloc.com/v1/wallet/healthKeep the contract current
The public API pages are built from the FabricBloc docs catalog. When fabricbloc-docs publishes a new public catalog, this site can rebuild the Scalar references without hand-editing endpoint facts. Start from /docs/api and open the service you need.