Public Fireblocks docs only
It draws from the public Fireblocks developer docs, SDKs, and support center. Nothing internal, no customer data, no invented numbers. It is not a portfolio chatbot.
Citepilot
A small assistant for developers integrating the Fireblocks SDKs and API. It answers from the public developer docs, and cites every claim so you can check the work. It is the same idea I build into real systems: route the question, pull from trusted sources, and never answer without evidence.
Ask about building on the Fireblocks SDKs and API.
I’m Citepilot. I answer implementation questions from the public Fireblocks developer docs, SDKs, and support center, and I cite every claim so you can check it. I run entirely in your browser. If a question falls outside those docs, I’ll say so rather than guess.
Browser-only prototype. It answers from a fixed set of public Fireblocks SDK and API documentation facts using a deterministic, client-side lookup. There is no language model and no live backend behind it. Illustrative of how I think about evidence-backed answers, not a production product surface.
It draws from the public Fireblocks developer docs, SDKs, and support center. Nothing internal, no customer data, no invented numbers. It is not a portfolio chatbot.
Each answer links back to the exact source it came from, so you can verify it yourself in one click instead of taking it on faith.
Retrieval is a small deterministic lookup running client-side. No backend, no API keys, no language model, and nothing you type leaves this page.
Hiring for a role where customer-facing engineering meets AI systems? Building AI workflows for a technical GTM or product team? Same answer: