Our mission is to make HakiAPI the default infrastructure core for Python API SDKs — and increasingly, for the agentic workloads built on top of them. Here's what's shipped, what's next, and where we're headed.
Public API Foundation
The base client and public API surface every later SDK is built on top of.
Cleaned up and stabilized the client's public interface (v1.0.5) ahead of the SDK integrations that followed.
Foundational fixes and version cleanup (v1.0.4).
Gmail & Calendar Integration
The first production SDKs on top of HakiAPI's core: Gmail and Google Calendar.
Initial GmailClient release for reading and managing Gmail via the API (v1.1.0).
Reworked Gmail into resource-based routing with a shared pagination core (v1.2.0).
New Calendar API client built on the same pagination core as Gmail (v1.2.2).
OAuth 2.0 Engine & Token Vault
A real auth layer: token refresh, persistent storage, and pagination hardening.
Full OAuth 2.0 flow with a persistent, atomic token store backing the Gmail and Calendar clients (v2.0.0).
Fixed a pagination bug surfaced by the new OAuth engine (v2.0.1).
GitHub Client & Async Core
A GraphQL-powered GitHub client, plus an async-first rewrite of the base client.
New GitHub client built on GraphQL instead of REST (v2.1.0).
Async-native base client, plus daily/weekly contribution stats in the GitHub client (v2.1.2).
Predictive Rate-Limit Governor
Built for agentic RAG and multi-agent workflows, where parallel tool calls can burn through rate limits fast. Turns HakiAPI from a passive client into a proactive traffic controller that paces requests before a 429 ever happens.
Reads remaining-quota and reset-time headers off every response to track consumption velocity in real time.
Tracks usage per endpoint in an internal sliding window, not just a global counter.
Paces and pauses outgoing requests locally for a micro-duration when velocity approaches a threshold, so the 429 never fires.
Pairs with HakiAPI's client-side circuit breaker: the breaker fast-fails on cascading 5xx outages while the Governor prevents 429s from happening in the first place.
Experimental ideas we're excited about, not yet scheduled or guaranteed.
A registry of community-maintained clients built on the HakiAPI core.
Generate a fully typed HakiAPI client directly from an OpenAPI spec.
Tracing built around multi-agent call graphs, not just single request/response pairs.
HakiAPI follows a stability-first release cycle. Core infrastructure is completed before new API integrations are added, ensuring every client inherits a consistent, well-tested foundation.