API Cheat Sheet: Faster Endpoint Discovery with Gemini & Kilo Code
This article describes how to use AI assistants like Gemini and Kilo Code to quickly find API endpoints, parameters, and whether an API key is required. It provides an example using the CoinGecko API to fetch Bitcoin price in ZAR on the VALR exchange, showing curl commands for both free and pro tiers. The author advocates relying on AI over manual doc reading, with a security note about using environment variables for API keys.
AI API Cheat Sheet: Faster Endpoint Discovery with Gemini & Kilo Code Let's talk Bitcoin (and sometimes Rust & AI)
Let's talk Bitcoin (and sometimes Rust & AI)
Tip me via Bitcoin LN: [email protected] <– You know what to do!
API Cheat Sheet
By Marius on July 6th, 2026
Scenario
You have a specific API you want to use but are not sure about the endpoint, the parameters, or whether it is public (no API key required) or private (requires an API key). All you know is the provider, and maybe you have access to the API docs.
But as all of us know, reading the documents and finding the exact right API call might be hit-and-miss, leaving you experimenting until you find the right one.
What to do?
Open your favourite AI client; for me, it is mostly Gemini or even Kilo Code, and enter your prompt.
Start by describing how you will use it, as a REST API called via curl, for example or in some programming language, for example, Rust. Specify the provider and what data you want included in the return.
Here is an example of a prompt I gave Gemini:
Using the CoinGecko API, give me a curl command to get the BTC price in ZAR on the VALR exchange
And here is Gemini’s response:
If you are using the CoinGecko Free API Tier, run this command
curl -X 'GET' \ 'https://api.coingecko.com/api/v3/exchanges/valr/tickers?coin_ids=bitcoin' \ -H 'accept: application/json'
If you are using a CoinGecko Pro API Key, use the pro domain and include your API key in the header:
curl -X 'GET' \ 'https://pro-api.coingecko.com/api/v3/exchanges/valr/tickers?coin_ids=bitcoin' \ -H 'accept: application/json' \ -H 'x-cg-pro-api-key: YOUR_API_KEY_HERE'
If you specify a programming language, your response will be much more detailed and will include what libraries or crates, if you use Rust, are dependencies and some skeleton code as a starting point for how to call the API in the language you specified.
I hardly ever read the docs anymore; my AI agents are my go-to at the moment. I only reference the docs when the result is not what I want, and the AI agent clearly went off the boil and cannot come up with the correct answer.
Security Note
If and when you use any secure items like API keys. Do not include it in the code that you share; use environment variables that are local and use the keys via the environment variables.
Categorized under: AI, Coding, Rust.
Tagged with: ai, curl, rust, software development.
Leave a Response
← Veteran Coder, Modern Delivery: The Hunt for the Perfect Technical TPM Role
add/remove ai bitcoin books cellphone compaq crossover crossover at work cryptocurrencies Dreamhost dropbox eclipse elon musk Google google calendar how to ibm install karmic kubuntu lenovo Linux microsoft network manager notes pdt php program management programming programs project management rust rust_bytes scrum master software development subversion sun synaptic sync Ubuntu Unix windows wordpress work xbmc
July 2026 (2)
June 2026 (1)
May 2026 (2)
April 2026 (1)
February 2026 (1)
November 2025 (2)
October 2025 (1)
July 2018 (1)
June 2018 (2)
January 2018 (1)
November 2017 (2)
March 2017 (1)
February 2017 (1)
October 2016 (2)
August 2016 (4)
July 2016 (6)
December 2012 (1)
June 2012 (2)
May 2012 (1)
April 2012 (1)
March 2012 (3)
February 2012 (4)
January 2012 (1)
December 2011 (1)
October 2011 (1)
September 2011 (2)
August 2011 (4)
May 2011 (2)
April 2011 (4)
December 2010 (1)
November 2010 (2)
October 2010 (5)
September 2010 (1)
August 2010 (5)
July 2010 (3)
June 2010 (5)
May 2010 (6)
April 2010 (3)
March 2010 (1)
January 2010 (1)
December 2009 (2)
November 2009 (3)
October 2009 (5)
September 2009 (10)
August 2009 (8)
July 2009 (3)
June 2009 (2)
May 2009 (1)
April 2009 (6)
March 2009 (3)
February 2009 (2)
January 2009 (11)
Marius (146)