How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Feedly

Feedly is a content aggregation and threat intelligence platform that reads millions of open sources and turns them into structured, machine-readable intelligence. Its consumer product is a feed reader built on RSS/Atom; its commercial product, Feedly Threat Intelligence, applies a family of AI models ("Leo") to build a Real-Time Threat Graph covering threat actors, malware families, CVEs, indicators of compromise, MITRE ATT&CK techniques, and cyberattacks. The Feedly API is a REST API over api.feedly.com/v3 that exposes those objects to security teams for SOAR/SIEM automation — collecting articles from AI Feeds, Folders and Boards, searching and asking questions of the corpus with LLMs, pulling CVE/malware/threat-actor insight cards and their relationships, exporting IoCs with context, and registering webhooks for saved-article and annotation events. Feedly also operates a hosted, OAuth-protected Model Context Protocol server over its Threat Graph, and publishes an open-source library of CTI Agent Skills and prompts for Claude.

agent ready

Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.

Kin Score

API Evangelist profiles Feedly the way a machine reads it — 27 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Feedly scores 67.2/100 (exemplar), with a separate agent-readiness read of 52/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 67.2/100 · exemplar
Contract Quality 15.7 / 25
Developer Ergonomics 13.0 / 20
Commercial Clarity 16.3 / 20
Operational Transparency 10.9 / 13
Governance 2.5 / 12
Discoverability 8.7 / 10
Agent readiness — 52/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics documented 4.0 / 8
Request/Response Examples 7.0 / 7
Rate-Limit Signaling documented 3.5 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Feedly Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Feedly's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/feedly/"
   title="Feedly on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/feedly.svg"
       alt="Feedly Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Feedly

Each block below is one kind of artifact we hold for Feedly. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 2

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Feedly API

REST API over api.feedly.com/v3 for the Feedly Threat Intelligence platform. Collect articles from AI Feeds, Folders and Boards by streamId; search and query the corpus with the...

Feedly Threat Graph MCP Server

Hosted, remote Model Context Protocol server exposing the Feedly Real-Time Threat Graph to AI agents. Feedly documents 16 tools covering threat actors, malware, vulnerabilities,...

Open Collections 18

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Feedly API

OPEN COLLECTION

Alerts API

OPEN COLLECTION

Annotations API

OPEN COLLECTION

Enterprise Collections

OPEN COLLECTION

Enterprise Users API

OPEN COLLECTION

Enterprise API

OPEN COLLECTION

Entities API

OPEN COLLECTION

Entries

OPEN COLLECTION

Get Intel Profiles

OPEN COLLECTION

IoCs

OPEN COLLECTION

Memes API

OPEN COLLECTION

ML Endpoint

OPEN COLLECTION

Search API

OPEN COLLECTION

Streams API

OPEN COLLECTION

Tags API

OPEN COLLECTION

TI Endpoints

OPEN COLLECTION

Trends API

OPEN COLLECTION

Scroll within the panel for all 18 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

feedly-mcp.yml

MCP SERVER

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.

Published pricing tiers and plan structures.

Feedly Plans Pricing

2 plans

PLANS

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Feedly Rate Limits

1 limits

RATE LIMITS

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Feedly Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Feedly Authentication

apiKey/http · 2 schemes

SECURITY

Feedly Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Feedly Trust Center

SOC 2 Type 1, SOC 2 Type 2

SECURITY

Resources

Every other property we hold for Feedly — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Company 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/feedly · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Feedly, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.