One unified API for GitHub, Hacker News, YouTube, and more. Pick the path that suits you — run a ready-made notebook in seconds, or follow the full setup guide.
Open a Google Colab, pick your LLM, and run every cell. Ideal for exploring Ohita with LangChain.
↓ ~5 minutes Full setup guideCreate an account, grab your API key, and make your first call from the terminal or your own code.
↓ ~3 minutes Agent integrationsWire Ohita into LangChain or CrewAI as a tool. Copy-paste examples that work out of the box.
↓Pick your LLM, open the notebook in Google Colab, and run every cell. You'll have a working Ohita integration before your coffee gets cold. Each notebook walks you through sign-up, getting an API key, and making real calls — all in one place.
Each notebook uses LangChain + Ohita. You only need a free Ohita API key and a provider key for the LLM you choose.
To create your free account.
A terminal, a browser, Python, JavaScript — anything that can call a URL.
That's it. No credit card, no app registration needed for most services. The free plan includes 2,500 requests/month — see pricing for higher limits. For Reddit, X/Twitter, Slack, and Brave, you'll also need your own API credentials — see the optional BYOK step below.
Head to the sign-up page and create an account with your email and a password.
Once you're logged in, go to your dashboard and click "Generate new key". You'll get a key that looks like this:
Copy it and save it somewhere safe. This single key gives you access to most services Ohita supports — GitHub, Hacker News, YouTube, GNews, Dev.to, Weather, Wikipedia, ArXiv, CoinGecko, Finnhub, Stack Exchange, Search (Tavily), and more. For Reddit, X/Twitter, Slack, and Brave, you'll need to store your own credentials first.
Now the fun part. Pick any example below, replace ok_live_YOUR_KEY with your actual key, and run it.
You just pulled live data from Hacker News through Ohita. The same key works for every other service too.
Just swap the endpoint. No extra setup needed.
Every call follows the same pattern: https://api.ohita.tech + the endpoint + your API key in the header. Reddit, X/Twitter, Slack, and Brave require you to store your own credentials first — see the BYOK step above.
Most services work out of the box. But if you want to use Reddit, X/Twitter, Slack, or Brave Search, or if you prefer to use your own quotas for any provider, you can store your own credentials. Ohita encrypts them at rest and uses them automatically on your requests.
You can test a credential before storing it:
Ohita is just a REST API. If your tool can make HTTP requests, it works with Ohita. No SDK required, no plugins to install.
Ohita is a plain REST API, so any agent framework can call it. Below are copy-paste examples for LangChain and CrewAI — or, if your agent already knows how to make HTTP calls, just point it at the docs.
Many AI agents (ChatGPT, Claude, Cursor, Windsurf, coding copilots) can make HTTP requests on their own. Just tell them: "Use the Ohita API at https://api.ohita.tech/v1. Docs are at https://api.ohita.tech/docs. My API key is ok_live_... — pass it as a Bearer token." That's enough for the agent to discover every endpoint and start calling them — no wrapper code needed.
Install dependencies:
Define Ohita endpoints as tools and run an agent:
Swap ChatOpenAI for ChatAnthropic or ChatGoogleGenerativeAI to use a different LLM — the Ohita tools stay the same.
Install dependencies:
Create tools, an agent, and kick off a crew:
CrewAI uses OpenAI by default. Set OPENAI_API_KEY in your environment, or pass a custom LLM to the Agent constructor.
Wrap any Ohita endpoint in a tool function with a docstring — the agent handles the rest. Add more tools for YouTube, Reddit, GNews, Dev.to, Wikipedia, CoinGecko, Finnhub, or any other Ohita endpoint. Or skip the code entirely and just give your agent the API docs URL.
Free account. One API key. Most services instantly, the rest with your own credentials.