is-agentic

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Is Agentic

Is Agentic runs a technical audit of a public URL and publishes a 0 to 100 agent-readiness score with evidence-backed issues and recommended fixes. All interfaces below are public, read-only, and free; none needs an API key.

Is Agentic 会对公共 URL 执行技术审计，并发布一个 0 到 100 分的 Agent 就绪度评分，同时提供有证据支持的问题和修复建议。以下所有接口均为公共、只读且免费，无需 API key。

Get a score

获取评分

Default: the official CLI. It returns a stored report immediately, or starts a scan and waits when none exists.

npx is-agentic <domain> --json

Omit

--json

only when a human is reading the terminal output.

When you cannot run commands, use the read-only API instead. It never starts a scan; a 404 means no completed report exists yet.

GET https://is-agentic.com/api/v1/report?url=<url-encoded-target>

MCP hosts can connect to the Streamable HTTP endpoint

https://is-agentic.com/mcp

and call

is_agentic_get_report

is_agentic_get_methodology

, or

is_agentic_get_developer_docs

默认方式：使用官方 CLI。如果已有报告，它会立即返回；如果没有，则会启动扫描并等待扫描完成。

npx is-agentic <domain> --json

仅当由人工阅读终端输出时，才可省略

--json

。

如果无法运行命令，请改用只读 API。该 API 不会启动扫描；返回 404 表示目前还没有已完成的报告。

GET https://is-agentic.com/api/v1/report?url=<url-encoded-target>

MCP 主机可以连接 Streamable HTTP 端点

https://is-agentic.com/mcp

，并调用

is_agentic_get_report

、

is_agentic_get_methodology

或

is_agentic_get_developer_docs

。

Read a report

读取报告

The JSON response is a

PublicScanReport

```
score
```
: 0 to 100, or
```
null
```
when the target could not be scored (for example an MCP server that requires authentication).
```
score_label
```
explains a null score.
```
score_breakdown.essential
```
and
```
.recommended
```
: each has
```
earned
```
,
```
available
```
,
```
passing
```
,
```
total
```
. Essential checks are the ones that matter most; a site can look polished and still fail them.
```
score_breakdown.bonus
```
:
```
points
```
and
```
positive_signals
```
. Bonus is additive and never required; do not treat missing bonus signals as defects.

issues[]

: each has

id

name

tier

(

essential

recommended

bonus

result

(

failed

partial

details

(evidence from the scan), and

recommendation

(the fix).

```
report_url
```
: the canonical human-readable report. Cite it when reporting a score to a person.
```
scanned_at
```
: when the audit ran. Reports are immutable snapshots.

JSON 响应是一个

PublicScanReport

：

```
score
```
：0 到 100；如果无法对目标进行评分，则为
```
null
```
，例如需要身份验证的 MCP server。
```
score_label
```
会解释 null 评分的原因。
```
score_breakdown.essential
```
和
```
.recommended
```
：两者都包含
```
earned
```
、
```
available
```
、
```
passing
```
、
```
total
```
。必要项检查是最重要的检查；一个网站即使看起来完善，也可能无法通过这些检查。
```
score_breakdown.bonus
```
：包含
```
points
```
和
```
positive_signals
```
。奖励项分数是额外附加的，永远不是必需项；不要将缺少奖励信号视为缺陷。
```
issues[]
```
：每项都包含
```
id
```
、
```
name
```
、
```
tier
```
（
```
essential
```
|
```
recommended
```
|
```
bonus
```
）、
```
result
```
（
```
failed
```
|
```
partial
```
）、
```
details
```
（扫描发现的证据）和
```
recommendation
```
（修复方法）。
```
report_url
```
：可供人工阅读的规范报告地址。向用户报告评分时应引用此地址。
```
scanned_at
```
：审计执行的时间。报告是不可变的快照。

Improve a site's score

提升网站评分

Fetch the report for the exact target you are improving.
Work through
```
issues
```
in this order:
```
essential
```
failures,
```
essential
```
partials, then
```
recommended
```
. Ignore
```
bonus
```
unless everything else passes.
For each issue,
```
details
```
says what the scan observed and
```
recommendation
```
says what to change. Prefer the recommendation; it was written against the actual evidence.
After deploying fixes, get a fresh score and compare
```
scanned_at
```
to confirm you are not reading the old snapshot (see gotchas).

获取正在改进的准确目标所对应的报告。
按照以下顺序处理
```
issues
```
：先处理
```
essential
```
失败项，再处理
```
essential
```
部分通过项，最后处理
```
recommended
```
项。除非其他所有检查都已通过，否则忽略
```
bonus
```
。
对于每个问题，
```
details
```
会说明扫描观察到的内容，
```
recommendation
```
会说明需要更改的内容。优先采用建议，因为它是根据实际证据编写的。
部署修复后，获取新的评分并比较
```
scanned_at
```
，以确认读取的不是旧快照（参见注意事项）。

Errors

错误

Failures are RFC 9457

application/problem+json

with a stable

code

and a

resolution

hint. Act on the code:

```
invalid_url
```
(400): pass a public HTTP or HTTPS URL.
```
report_not_found
```
(404): no completed report exists; create one with the CLI, or open
```
https://is-agentic.com/scan/<target>
```
to start a scan, then retry after it completes.
```
rate_limit_exceeded
```
(429): honor
```
Retry-After
```
before retrying.
```
report_temporarily_unavailable
```
(503): retry shortly; do not start a new scan.

失败响应采用 RFC 9457

application/problem+json

格式，包含稳定的

code

和

resolution

提示。请根据

code

采取相应操作：

```
invalid_url
```
（400）：传入公共 HTTP 或 HTTPS URL。
```
report_not_found
```
（404）：不存在已完成的报告；使用 CLI 创建报告，或打开
```
https://is-agentic.com/scan/<target>
```
启动扫描，然后在扫描完成后重试。
```
rate_limit_exceeded
```
（429）：重试前遵循
```
Retry-After
```
。
```
report_temporarily_unavailable
```
（503）：稍后重试；不要启动新的扫描。

Gotchas

注意事项

Reports refresh only when a visit finds them older than 6 hours. Re-running the CLI right after deploying a fix returns the same stored snapshot; check
```
scanned_at
```
before drawing conclusions, and use the Rescan control on the report page when a human needs an immediate re-run.
The API and the CLI differ on missing reports: the API returns 404, the CLI starts a scan and waits. Pick accordingly.
Targets are exact:
```
example.com/docs
```
and
```
example.com
```
are separate reports, and a URL with a query string is its own report.
The rate limit is 120 requests per IP per 60 seconds.
For token-light reading, content pages and completed reports honor
```
Accept: text/markdown
```
.

只有在访问时发现报告已有 6 小时以上，报告才会刷新。部署修复后立即重新运行 CLI 会返回相同的存储快照；得出结论前请检查
```
scanned_at
```
，如果人工需要立即重新运行，请使用报告页面上的 Rescan 控件。
API 和 CLI 对缺失报告的处理方式不同：API 返回 404，CLI 则启动扫描并等待。请根据实际情况选择。
目标是精确匹配的：
```
example.com/docs
```
和
```
example.com
```
对应不同报告，带有 query string 的 URL 也对应独立报告。
速率限制为每个 IP 每 60 秒 120 个请求。
如需减少 token 消耗，内容页面和已完成的报告支持
```
Accept: text/markdown
```
。