Repository, build, lint, test and code-understanding services that an agent can call while working in a codebase.
Does a website use GitHub gist? Fetches the page (homepage for a bare domain) and matches GitHub gist's fingerprints in the HTML and response headers, returning yes/no with the evidence snippet and the category (embeds)....
Change watch for does site use github pages: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that chan...
Change watch for does site use github embed: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that chan...
Change watch for does site use codepen: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that changed w...
Find the github page of a website: fetches the homepage, scans link text and URLs for github patterns and returns the best candidate URL(s) with the anchor text, plus a confidence. Agents use it to land on the right page...
Fetch the verified ABI for a contract address from Sourcify, plus a ready-to-use list of human-readable function signatures with their 4-byte selectors. Covers 8 EVM mainnets. Unverified contracts return a structured {ve...
Change watch for extract github repo stats: runs the check, compares it with the result from your previous call for the same url (kept 90 days) and returns the current answer, changed true/false, the fields that changed...
How many <code> elements does the page have? Fetches the URL and counts code tags (plus, where relevant, how many have alt/src/href/type attributes), and the page's total element count for scale. Structural audits and te...
Change watch for extract github repos from page: runs the check, compares it with the result from your previous call for the same url (kept 90 days) and returns the current answer, changed true/false, the fields that cha...
Change watch for extract zip codes us from page: runs the check, compares it with the result from your previous call for the same url (kept 90 days) and returns the current answer, changed true/false, the fields that cha...
Change watch for extract postal codes ca from page: runs the check, compares it with the result from your previous call for the same url (kept 90 days) and returns the current answer, changed true/false, the fields that...
Bulk extract github readme headings: up to 20 urls in one call, processed concurrently, results in input order with a per-item error field and a failure count. Same answer per item as the single endpoint. Batch enrichmen...
Bulk extract github repo stats: up to 20 urls in one call, processed concurrently, results in input order with a per-item error field and a failure count. Same answer per item as the single endpoint. Batch enrichment for...
HTTP 100 Continue: what it means (the client may send the request body), what a client should do (continue sending), the class it belongs to, whether it is retryable and idempotency-safe, the defining RFC, and common cau...
HTTP 101 Switching Protocols: what it means (upgrade accepted (e.g. WebSocket)), what a client should do (switch protocol), the class it belongs to, whether it is retryable and idempotency-safe, the defining RFC, and com...
HTTP 102 Processing: what it means (WebDAV: still working), what a client should do (wait), the class it belongs to, whether it is retryable and idempotency-safe, the defining RFC, and common causes. Precise one-code ref...
HTTP 103 Early Hints: what it means (preload hints before the final response), what a client should do (start preloading), the class it belongs to, whether it is retryable and idempotency-safe, the defining RFC, and comm...
HTTP 200 OK: what it means (success), what a client should do (use the body), the class it belongs to, whether it is retryable and idempotency-safe, the defining RFC, and common causes. Precise one-code reference for err...
HTTP 201 Created: what it means (resource created; Location points at it), what a client should do (read Location), the class it belongs to, whether it is retryable and idempotency-safe, the defining RFC, and common caus...
HTTP 202 Accepted: what it means (queued for async processing), what a client should do (poll the status URL), the class it belongs to, whether it is retryable and idempotency-safe, the defining RFC, and common causes. P...
HTTP 203 Non-Authoritative Information: what it means (transformed by a proxy), what a client should do (use with care), the class it belongs to, whether it is retryable and idempotency-safe, the defining RFC, and common...
HTTP 204 No Content: what it means (success with empty body), what a client should do (nothing to parse), the class it belongs to, whether it is retryable and idempotency-safe, the defining RFC, and common causes. Precis...
HTTP 205 Reset Content: what it means (reset the form/view), what a client should do (reset UI), the class it belongs to, whether it is retryable and idempotency-safe, the defining RFC, and common causes. Precise one-cod...
HTTP 206 Partial Content: what it means (range request served), what a client should do (assemble ranges), the class it belongs to, whether it is retryable and idempotency-safe, the defining RFC, and common causes. Preci...