Skip to content
Back to search

agentic-ai-apis

The ultimate collection of APIs for building autonomous AI agents — 2,036 production-ready APIs across Agents, AI Models, and MCP Servers. Stop wasting weeks building infrastructure. Plug these in and ship your agent today.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/cporter202/agentic-ai-apis with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/cporter202/agentic-ai-apis'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/cporter202--agentic-ai-apis/badge.svg)](/listings/cporter202--agentic-ai-apis)

HTML

<a href="/listings/cporter202--agentic-ai-apis"><img src="/api/listings/cporter202--agentic-ai-apis/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 157 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. <img src="./assets/readme-hero-v2.svg" alt="agentic-ai-apis hero banner" width="100%" />
  3. <br />
  4. <br />
  5. [![GitHub stars](https://img.shields.io/github/stars/cporter202/agentic-ai-apis?style=for-the-badge)](https://github.com/cporter202/agentic-ai-apis/stargazers)
  6. [![GitHub forks](https://img.shields.io/github/forks/cporter202/agentic-ai-apis?style=for-the-badge)](https://github.com/cporter202/agentic-ai-apis/network/members)
  7. [![Last commit](https://img.shields.io/github/last-commit/cporter202/agentic-ai-apis?style=for-the-badge)](https://github.com/cporter202/agentic-ai-apis/commits/main)
  8. [![Repo size](https://img.shields.io/github/repo-size/cporter202/agentic-ai-apis?style=for-the-badge)](https://github.com/cporter202/agentic-ai-apis)
  9. <p>
  10. <a href="#at-a-glance"><strong>At A Glance</strong></a>
  11. |
  12. <a href="#start-here"><strong>Start Here</strong></a>
  13. |
  14. <a href="#explore-the-stack"><strong>Explore The Stack</strong></a>
  15. |
  16. <a href="#why-this-repo-wins"><strong>Why This Repo Wins</strong></a>
  17. |
  18. <a href="#star-history"><strong>Star History</strong></a>
  19. </p>
  20. </div>
  21. ## At A Glance
  22. > The ultimate collection of APIs for building autonomous AI agents - **3,030 production-ready APIs** across **Agents**, **AI Models**, and **MCP Servers**.
  23. This repository is designed to feel like a launchpad, not a junk drawer. It is tightly scoped around the API layers that matter most when you are building autonomous systems, copilots, tool-using assistants, and MCP-native workflows.
  24. | Metric | Count |
  25. |--------|-------|
  26. | Total APIs | 3,030 |
  27. | Categories | 3 |
  28. | Last Updated | 2026-11-17 |
  29. | Focus | Agentic AI infrastructure |
  30. <table>
  31. <tr>
  32. <td width="33%" valign="top">
  33. <h3>Agents</h3>
  34. <p><strong>803 APIs</strong></p>
  35. <p>Execution layers, orchestration, autonomous task handling, and agent-style workflows.</p>
  36. <p><a href="./agents-apis/"><strong>Open Agents Directory</strong></a></p>
  37. </td>
  38. <td width="33%" valign="top">
  39. <h3>AI Models</h3>
  40. <p><strong>1,757 APIs</strong></p>
  41. <p>Generation, reasoning, extraction, transformation, and model-powered product building blocks.</p>
  42. <p><a href="./ai-models-apis/"><strong>Open AI Models Directory</strong></a></p>
  43. </td>
  44. <td width="33%" valign="top">
  45. <h3>MCP Servers</h3>
  46. <p><strong>470 APIs</strong></p>
  47. <p>Model Context Protocol integrations that connect assistants to real tools, systems, and data.</p>
  48. <p><a href="./mcp-servers-apis/"><strong>Open MCP Servers Directory</strong></a></p>
  49. </td>
  50. </tr>
  51. </table>
  52. ## Start Here
  53. 1. Pick the layer you need first: `Agents`, `AI Models`, or `MCP Servers`.
  54. 2. Open that category README and scan the API names and descriptions.
  55. 3. Click through to the provider page for implementation details, pricing, and docs.
  56. 4. Build your shortlist fast instead of wasting hours digging through irrelevant categories.
  57. ## Explore The Stack
  58. <details open>
  59. <summary><strong>Agents</strong></summary>
  60. Best for builders who need APIs that feel closer to execution and autonomy:
  61. - agent workflows
  62. - orchestration layers
  63. - autonomous task completion
  64. - assistant behavior and action loops
  65. [Browse Agents APIs](./agents-apis/)
  66. </details>
  67. <details>
  68. <summary><strong>AI Models</strong></summary>
  69. Best for builders who need intelligence and generation as a reusable service layer:
  70. - reasoning and inference
  71. - summarization and extraction
  72. - content generation
  73. - analysis and transformation
  74. [Browse AI Models APIs](./ai-models-apis/)
  75. </details>
  76. <details>
  77. <summary><strong>MCP Servers</strong></summary>
  78. Best for builders who want agents to use tools through structured interfaces:
  79. - MCP-native tool integrations
  80. - external system connectivity
  81. - docs, search, analytics, scheduling, and developer workflows
  82. - assistants that need real-world actions
  83. [Browse MCP Servers APIs](./mcp-servers-apis/)
  84. </details>
  85. ## Built For
  86. <table>
  87. <tr>
  88. <td width="25%" align="center"><strong>Autonomous Assistants</strong></td>
  89. <td width="25%" align="center"><strong>AI Copilots</strong></td>
  90. <td width="25%" align="center"><strong>MCP Toolchains</strong></td>
  91. <td width="25%" align="center"><strong>Internal Automation</strong></td>
  92. </tr>
  93. <tr>
  94. <td width="25%" align="center"><strong>Research Agents</strong></td>
  95. <td width="25%" align="center"><strong>Workflow Engines</strong></td>
  96. <td width="25%" align="center"><strong>Tool-Using LLM Apps</strong></td>
  97. <td width="25%" align="center"><strong>Production AI Features</strong></td>
  98. </tr>
  99. </table>
  100. ## Why This Repo Wins
  101. - It is opinionated. This repo is not trying to be every API category on earth.
  102. - It is agent-native. Everything revolves around the stack needed for autonomous AI systems.
  103. - It is faster to use. The clutter is gone, so discovery is dramatically easier.
  104. - It is better positioned. The repo name, README, and categories now all tell the same story.
  105. ## Scope Guarantee
  106. This repository intentionally includes only:
  107. - **Agents** for execution, orchestration, planning, and autonomous workflows
  108. - **AI Models** for inference, generation, analysis, and reasoning
  109. - **MCP Servers** for exposing tools and systems to AI assistants through MCP
  110. Anything outside those three categories has been removed from the tracked repository structure.
  111. ## Star History
  112. [![Star History Chart](https://api.star-history.com/svg?repos=cporter202/agentic-ai-apis&type=Date)](https://www.star-history.com/#cporter202/agentic-ai-apis&Date)
  113. ## Maintenance Notes
  114. - A GitHub Actions workflow now syncs the Apify catalog daily and commits only when upstream data actually changes.
  115. - The generation scripts in [settings](./settings/) are configured to rebuild only the three tracked categories above.
  116. - The visual README layout is now part of the repo's default presentation, not just a temporary pass.
  117. - API links keep the existing affiliate tracking from the upstream source data.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.