The First API-Centric Observability Platform

How do you know if a small code change can take down your site? What's really going on with your APIs? At Akita, we're building tools to help you answer that question.

Akita watches calls to web APIs in order to help you visualize your service graph, monitor your APIs, make sense of your request/response logs, and 💥 catch breaking changes 💥.

By passively watching traffic, Akita integrates in a low-friction, low-risk way, making it possible to run in CI/CD, staging, or production without too much overhead. Akita's API modeling technology to automatically catch breaking changes.

Get Started    FAQs

Agent with Postman Collections

Akita easily integrates with Postman to generate API specs from your Postman Collections.

Step 1: Run Akita CLI

Run the Akita CLI on the same machine as the one where your Postman Collections run. You will need to know which port that requests in your postman collections use to connect to your API (e.g. port 80).

akita learn \
  --service my-service \
  --filter "port {PORT}"

Step 2: Run Your Postman Collection

Simply hit "Run" and you're all set.

Relevant docs from Postman: https://learning.postman.com/docs/running-collections/intro-to-collection-runs/#starting-a-collection-run

Step 3: Stop Akita CLI

Stop Akita CLI by sending SIGINT (Ctrl-C) to the process. You should get a link to your API spec!

Updated 4 months ago


Agent with Postman Collections


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.