The wallet API launch path should start with docs
Why FabricBloc's wallet experience should connect quickstarts, REST reference, SDK notes, and agent workflows from one docs entry point.
walletsapiquickstart
A builder should not have to guess where to start. The docs path should connect the product promise to a quickstart, then to REST API reference, SDK integration notes, and agent workflows for teams using MCP-aware tools.
The content catalog helps keep that path explicit. Guide pages can explain the launch sequence, while generated API pages stay anchored to service-owned OpenAPI and reviewed examples.
Next step
Read the docs quickstart
Why FabricBloc's wallet experience should connect quickstarts, REST reference, SDK notes, and agent workflows from one docs entry point.
Continue