---
name: ietf-agentic
description: >-
  Answer "any new agentic AI drafts lately?", "what changed in the agentic AI
  landscape", "new IETF drafts on agents / MCP / A2A / agent identity", or
  requests to summarise recent agentic-AI Internet-Drafts. Reads the JSON and
  markdown digest API behind ietf.jaime.win/agentic-ai-new (scan runs four
  times a day, classified by typesafe/jev). Do NOT use for reviewing a draft's
  text (draft-review), CoAP specifics (ietf-core), or live meeting notes
  (ietf-live-notes).
---

# IETF agentic AI drafts: digest API

ietf.jaime.win keeps two things current from the datatracker: the curated
landscape at `/agentic-ai-drafts` (about 100 RFCs and drafts, hand-picked) and
a radar at `/agentic-ai-new` (every draft posted or revised in the last three
days, prefiltered for AI terms, scored by `typesafe/jev` for relevance,
section and centrality). Both are exposed read-only, no auth, CORS open.

Start here, it answers "anything new lately" in one call:

```bash
curl -s "https://ietf.jaime.win/api/agentic/digest?since=7d&format=md"
```

Returns markdown with (1) new candidates in the window above the relevance
threshold, each with title, section, relevance, centrality, the "Is it AI?"
style verdict when scored, and links, (2) curated drafts that got a new
revision, expired, were replaced or published, (3) last scan time. Drop
`format=md` for JSON. `since` takes `36h`, `3d`, `2w` or an ISO date; `min`
sets the relevance threshold (default 0.7); `limit` caps candidates (max 40).

Other endpoints (full self-description at `https://ietf.jaime.win/api/agentic`):

```bash
# filtered candidates, style verdicts joined
curl -s "https://ietf.jaime.win/api/agentic/candidates?section=identity&min=0.8&style=1"
# params: since, min, section (identity|authz|discovery|protocols|netmgmt|attestation|iot|other),
#         centrality (0|1|2 minimum), submitter (e.g. das), q (substring), sort (time|relevance|found), limit
# curated drafts whose revision or state changed
curl -s "https://ietf.jaime.win/api/agentic/changes?since=14d"
# live state of every curated draft, last scan summary, Atom feed
curl -s https://ietf.jaime.win/api/agentic/state
curl -s https://ietf.jaime.win/api/agentic/status
curl -s https://ietf.jaime.win/api/agentic/feed.xml
```

## How to answer

- Default window is the last 7 days; use what the user asked ("this month" = `30d`, "since IETF 126" = the ISO date).
- Lead with the count and the two or three most relevant candidates (highest relevance, centrality "primary subject"), one line each: name, title, section, why it matters in plain words taken from the abstract. Then the curated changes. Then a link to the page.
- Say it is a classifier's view of the abstract, not a review, when the user may act on it. Skip that caveat for casual chat.
- A flood from one submitter (the digest shows the same name prefix many times) is worth one sentence, not one line per draft. Mention how many and the theme.
- If the user wants details on one draft, fetch `https://datatracker.ietf.org/doc/html/<name>` and read it; do not paraphrase the abstract as if it were the draft.
- Writing style of the answer follows `writing-rules`: plain sentences, no bullets with more than two lines, wikilinks only when writing into Obsidian.