メニュー
Use when the user asks about quota, billing visibility, or processed-page counts. Covers GET /v1/usage — query params, response shape, when to report usage proactively to the user.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use when extracting a page needs scripted interaction first — click, type, press a key, scroll, wait, screenshot, or run JS before capturing the DOM. Covers `crawlberg interact <url> --actions` with the real action schema, result shape, limits, and external-CDP options.
Crawl, scrape, and convert websites to Markdown using the local crawlberg CLI and its MCP server. Use when the user wants to fetch a page, follow links across a domain, enumerate URLs, or drive a real browser. Covers installation, the subcommands (scrape, crawl, map, interact, mcp, serve), output formats (JSON + Markdown), browser fallback, and when to prefer the MCP server over shelling out.
Use when the user wants to follow links across a domain and capture every reachable page as Markdown. Covers `crawlberg crawl` with depth, page caps, concurrency, rate limiting, domain scoping, robots, and output selection.
Use when a static fetch returns nothing useful and the page needs a real browser. Covers `--browser-mode auto|always|never`, external CDP via `--browser-endpoint`, symptoms of JS-only pages and WAF blocks, and the performance cost.
Use when the user wants the list of URLs on a site rather than the page content — sitemap analysis, link planning, or seeding another tool. Covers `crawlberg map <url>` with `--limit`, `--search`, robots, output, and how it differs from a full crawl.
Use when the user wants a single page rendered as clean Markdown plus structured metadata. Covers `crawlberg scrape <url>`, JSON vs Markdown output, what metadata is returned, and how to handle JS-heavy pages.
| name | managing-cloud-usage |
| description | Use when the user asks about quota, billing visibility, or processed-page counts. Covers GET /v1/usage — query params, response shape, when to report usage proactively to the user. |
GET /v1/usage is the only endpoint for quota and billing visibility.
It returns aggregate counters for the queried period plus the remaining
quota for the project.
GET https://api.xberg.io/v1/usage
Authorization: Bearer $KREUZBERG_API_KEY
| Param | Format | Default |
|---|---|---|
start | ISO-8601 date (e.g. 2026-03-01) | First day of current month. |
end | ISO-8601 date (e.g. 2026-04-01) | First day of next month. |
Both are optional. Omit both for the current calendar month.
{
"period_start": "2026-05-01",
"period_end": "2026-06-01",
"total_pages": 5432,
"total_documents": 87,
"total_failed": 2,
"quota_limit": 100000,
"quota_remaining": 94568,
"by_mime_type": {
"application/pdf": { "documents": 65, "pages": 3200, "failed": 1 },
"image/png": { "documents": 15, "pages": 1800, "failed": 0 },
"text/plain": { "documents": 7, "pages": 432, "failed": 1 }
}
}
total_pages — pages billed in the period. The unit of cost.total_documents — files submitted, regardless of page count.total_failed — extractions that ended in failed status. Failed
jobs do not consume quota.quota_limit / quota_remaining — total and remaining pages on the
current plan.by_mime_type — per-MIME breakdown. Useful for identifying which
document types drive cost.curl -s https://api.xberg.io/v1/usage \
-H "Authorization: Bearer $KREUZBERG_API_KEY" | jq .
curl -s "https://api.xberg.io/v1/usage?start=2026-01-01&end=2026-02-01" \
-H "Authorization: Bearer $KREUZBERG_API_KEY" | jq .
curl -s https://api.xberg.io/v1/usage \
-H "Authorization: Bearer $KREUZBERG_API_KEY" \
| jq '.quota_remaining * 100 / .quota_limit'
Pull usage proactively when:
quota_remaining
after submit so the user can see the impact.429 response includes a quota-exhausted error — surface the usage
shape so the user can decide whether to upgrade.Don't report usage on every routine extraction — it's noise.
| Status | Cause |
|---|---|
400 | start or end not ISO-8601, or end <= start. |
401 | Bad API key. |