Knowledge your agent can cite.
Search source-linked facts, inspect versions, and connect your agent over MCP or HTTP. Public reads need no account.
Try a lookup
Search public datasets and get passages you can trace to their source. No account or API key needed.
429 Too Many Requests
HTTP 429 Too Many Requests is a 4xx client error status code in the IANA HTTP Status Code Registry. - Code: 429 - Reason phrase: Too Many Requests - Class: 4xx (Client Error) - Defined in: RFC 6585
Read passage
HTTP 429 Too Many Requests is a 4xx client error status code in the IANA HTTP Status Code Registry. - Code: 429 - Reason phrase: Too Many Requests - Class: 4xx (Client Error) - Defined in: RFC 6585
431 Request Header Fields Too Large
HTTP 431 Request Header Fields Too Large is a 4xx client error status code in the IANA HTTP Status Code Registry. - Code: 431 - Reason phrase: Request Header Fields Too Large - Class: 4xx (Client Error) - Defined in: RF…
Read passage
HTTP 431 Request Header Fields Too Large is a 4xx client error status code in the IANA HTTP Status Code Registry. - Code: 431 - Reason phrase: Request Header Fields Too Large - Class: 4xx (Client Error) - Defined in: RFC 6585
414 URI Too Long
HTTP 414 URI Too Long is a 4xx client error status code in the IANA HTTP Status Code Registry. - Code: 414 - Reason phrase: URI Too Long - Class: 4xx (Client Error) - Defined in: RFC 9110, Section 15.5.15
Read passage
HTTP 414 URI Too Long is a 4xx client error status code in the IANA HTTP Status Code Registry. - Code: 414 - Reason phrase: URI Too Long - Class: 4xx (Client Error) - Defined in: RFC 9110, Section 15.5.15
421 Misdirected Request
HTTP 421 Misdirected Request is a 4xx client error status code in the IANA HTTP Status Code Registry. - Code: 421 - Reason phrase: Misdirected Request - Class: 4xx (Client Error) - Defined in: RFC 9110, Section 15.5.20
Read passage
HTTP 421 Misdirected Request is a 4xx client error status code in the IANA HTTP Status Code Registry. - Code: 421 - Reason phrase: Misdirected Request - Class: 4xx (Client Error) - Defined in: RFC 9110, Section 15.5.20
400 Bad Request
HTTP 400 Bad Request is a 4xx client error status code in the IANA HTTP Status Code Registry. - Code: 400 - Reason phrase: Bad Request - Class: 4xx (Client Error) - Defined in: RFC 9110, Section 15.5.1
Read passage
HTTP 400 Bad Request is a 4xx client error status code in the IANA HTTP Status Code Registry. - Code: 400 - Reason phrase: Bad Request - Class: 4xx (Client Error) - Defined in: RFC 9110, Section 15.5.1
Explore the public catalog
Browse science, web standards, and agent integration references. Each dataset describes its coverage, publisher, and review process; each document links to its original source.
| Dataset | Type | Documents | Version |
|---|---|---|---|
Agent integration referenceSource-linked implementation notes on MCP connections, tool results, and HTTP retries. Scoped to MCP 2025-11-25; not a general knowledge corpus. | Reference | ||
Android Kotlin best practicesSource-linked guidance on Android Kotlin fundamentals: Kotlin idioms, coroutines and flows, Jetpack Compose basics, architecture and ViewModels, and testing. Scoped to current Android Kotlin docs. | Reference | ||
Angular best practicesSource-linked guidance on modern Angular fundamentals: components, signals, dependency injection, templates, and reactive forms. Scoped to standalone Angular; not an NgModule-era corpus. | Reference | ||
Ansible best practicesSource-linked guidance on Ansible fundamentals: playbooks, inventory, variable precedence, handlers, and roles. Scoped to Ansible community documentation; not a general IT automation corpus. | Reference | ||
Apache Airflow best practicesSource-linked guidance on Apache Airflow fundamentals: DAGs and tasks, operators and sensors, scheduling, connections and variables, and production deployment. Scoped to current Apache Airflow docs. | Reference | ||
Astro best practicesSource-linked guidance on Astro fundamentals: islands architecture, components, pages and routing, content collections, and shipping less JavaScript. Scoped to current Astro; not a general static-site corpus. | Reference | ||
Bash best practicesSource-linked guidance on Bash scripting fundamentals: quoting, shell options with set, conditional constructs, parameter expansion, and arrays. Scoped to Bash as documented in the GNU Bash Reference Manual; not a general POSIX sh corpus. | Reference | ||
CSS best practicesSource-linked guidance on CSS layout and cascade fundamentals: flexbox, grid, specificity, custom properties, and media queries. Scoped to CSS; not a general web design corpus. | Reference | ||
dbt best practicesSource-linked guidance on dbt fundamentals: project structure, models and materializations, tests and documentation, sources and refs, and deployment. Scoped to current dbt docs. | Reference | ||
Django best practicesSource-linked guidance on Django fundamentals: models, migrations, lazy QuerySets, URL routing, and the template layer. Scoped to Django; not a general Python corpus. | Reference | ||
Docker best practicesSource-linked guidance on Dockerfile and image fundamentals: multi-stage builds, build context, layer caching, non-root users, and base image hygiene. Scoped to building images with BuildKit; not a runtime orchestration corpus. | Reference | ||
Docker Compose best practicesSource-linked guidance on Docker Compose fundamentals: the application model, the compose file, networking, profiles, and building images. Scoped to current Compose. | Reference | ||
ESLint best practicesSource-linked guidance on ESLint flat config fundamentals: configuration files, rule severity, plugins, ignoring files, and CLI autofix. Scoped to ESLint; not a general JavaScript style corpus. | Reference | ||
Express best practicesSource-linked guidance on Express fundamentals: routing, middleware, error-handling middleware, and production security and performance. Scoped to Express per the current official documentation; not a general Node.js corpus. | Reference | ||
FastAPI best practicesSource-linked guidance on FastAPI fundamentals: typed path parameters and Pydantic validation, dependency injection with Depends, async path operations, response models, and error handling with HTTPException. Scoped to FastAPI; not a general Python web corpus. | Reference | ||
Flutter best practicesSource-linked guidance on Flutter fundamentals: widgets, layout, state management, async Dart, and testing. Scoped to current Flutter and Dart docs. | Reference | ||
Git best practicesSource-linked guidance on Git fundamentals: branching workflows, rewriting history, rebasing versus merging, remote-tracking branches, and distributed workflows. Scoped to Git; not a hosting-platform or GitHub-specific corpus. | Reference | ||
GitHub Actions best practicesSource-linked guidance on GitHub Actions: workflow triggers and schedules, runner selection, dependency caching, secrets and environments, and security hardening. Scoped to GitHub Actions; not a general CI/CD corpus. | Reference | ||
Go best practicesSource-linked guidance on Go fundamentals from go.dev: error handling, gofmt formatting, goroutines and channels, naming conventions, and module dependency management. Scoped to Go; not a general programming corpus. | Reference | ||
GraphQL best practicesSource-linked guidance on GraphQL fundamentals: the type system and SDL, query and mutation operations, resolver execution, cursor-based pagination, and nullability and error design. Scoped to specification-level concepts; not tied to any server framework or client library. | Reference | ||
gRPC best practicesSource-linked guidance on gRPC fundamentals: protocol buffer service definitions, the four RPC types, deadlines, error status codes, and performance practices. Scoped to gRPC core concepts; not a language-specific tutorial corpus. | Reference | ||
Helm best practicesSource-linked guidance on Helm fundamentals: releases, charts, templates, values files, and chart best practices. Scoped to Helm 3. | Reference | ||
Java best practicesSource-linked guidance on Java fundamentals: classes and interfaces, collections, exceptions, concurrency, and streams. Scoped to current Java docs. | Reference | ||
Jest best practicesSource-linked guidance on Jest testing fundamentals: expect matchers, mock functions and modules, setup and teardown hooks, snapshot testing, and asynchronous tests. Scoped to Jest; not a general JavaScript testing corpus. | Reference | ||
JWT best practicesSource-linked guidance on securing JSON Web Tokens: explicit algorithm validation, issuer/audience/expiry checks, key entropy, claim contents, and token lifetimes. Scoped to JWT security per RFC 8725 and RFC 7519; not a general authentication corpus. | Reference | ||
Kafka best practicesSource-linked guidance on Apache Kafka fundamentals: partitions and replication, consumer groups, delivery semantics, retention, and producer configuration. Scoped to Apache Kafka (4.3 documentation); not a general messaging corpus. | Reference | ||
Koskamo agent APIHow agents retrieve facts, speak MCP, and propose revisions for approval. | Reference | ||
Koskamo docsOfficial public facts about Koskamo for agents to retrieve and cite. | Reference | ||
Kubernetes best practicesSource-linked guidance on core Kubernetes practice: resource requests and limits, health probes, namespaces, ConfigMaps, and labels. Scoped to upstream Kubernetes documentation; not an operator- or distribution-specific corpus. | Reference | ||
Laravel best practicesSource-linked guidance on Laravel fundamentals: routing, Eloquent, migrations, Blade templates, and middleware. Scoped to current Laravel; not a PHP language corpus. | Reference | ||
MongoDB best practicesSource-linked guidance on MongoDB fundamentals: the document data model, indexes, the aggregation pipeline, schema validation, and write concerns. Scoped to MongoDB; not a general database corpus. | Reference | ||
MySQL best practicesSource-linked guidance on MySQL 8.4 fundamentals: indexes, EXPLAIN execution plans, the InnoDB engine, constraint handling, and SELECT optimization. Scoped to MySQL 8.4; not a general SQL corpus. | Reference | ||
Next.js best practicesSource-linked guidance on Next.js 16 App Router fundamentals: server components, caching, metadata, images, and route handlers. Scoped to Next.js 16; not a general React corpus. | Reference | ||
nginx best practicesSource-linked guidance on nginx fundamentals: configuration structure and server blocks, reverse proxying with proxy_pass, response caching, gzip compression, and serving static files. Scoped to nginx; not a general web server corpus. | Reference | ||
Node.js best practicesSource-linked guidance on Node.js fundamentals: ES modules, the built-in test runner, environment configuration, unhandled rejections, and signal-driven shutdown. Scoped to current Node.js LTS; not a general JavaScript corpus. | Reference | ||
OAuth 2.0 best practicesSource-linked guidance on OAuth 2.0 security best current practice: PKCE, exact redirect URI matching, CSRF protection with state, bearer token handling and storage, and sender-constrained tokens. Scoped to OAuth 2.0 security per RFC 9700; not a general OAuth tutorial. | Reference | ||
OpenTelemetry best practicesSource-linked guidance on OpenTelemetry fundamentals: traces and spans, metrics, logs, collectors, and instrumentation. Scoped to current OpenTelemetry docs. | Reference | ||
pandas best practicesSource-linked guidance on pandas fundamentals: dataframes and indexing, groupby and aggregation, merging and joining, missing data, and performance and dtypes. Scoped to current pandas docs. | Reference | ||
Playwright best practicesSource-linked guidance on Playwright test fundamentals: isolation and parallelism, resilient locators, auto-retrying assertions, fixtures, and trace-based debugging. Scoped to Playwright Test; not a general browser-automation corpus. | Reference | ||
Polars best practicesSource-linked guidance on Polars fundamentals: lazy vs eager, expressions, selectors, joins and groupby, and streaming and performance. Scoped to current Polars docs. | Reference | ||
PostgreSQL best practicesSource-linked guidance on PostgreSQL fundamentals: EXPLAIN query plans, index types, transaction isolation, table constraints, and routine vacuuming. Scoped to the current PostgreSQL documentation; not a version-specific tuning corpus. | Reference | ||
Prisma best practicesSource-linked guidance on Prisma ORM fundamentals: data modeling in the contract file, the migration workflow, relation queries, index configuration, and transactions. Scoped to Prisma ORM 8 (the indexes page covers v7); not a general SQL corpus. | Reference | ||
Prometheus best practicesSource-linked guidance on Prometheus fundamentals: metric and label naming, instrumentation, alerting, histograms versus summaries, and recording rules. Scoped to Prometheus; not a general monitoring or PromQL corpus. | Reference | ||
Python best practicesSource-linked guidance on Python 3 fundamentals: virtual environments, type hints, pathlib, context managers, and exception handling. Scoped to Python 3; not a general-purpose language reference. | Reference | ||
RabbitMQ best practicesSource-linked guidance on RabbitMQ fundamentals: queue durability, exchange routing, consumer acknowledgements, TTL and dead lettering, and connection/channel management. Scoped to RabbitMQ; not a general AMQP or messaging corpus. | Reference | ||
Rails best practicesSource-linked guidance on Ruby on Rails fundamentals: Active Record, routing, migrations, associations, and testing. Scoped to current Rails guides. | Reference | ||
React best practicesSource-linked guidance on React fundamentals: rules of Hooks, avoiding unnecessary Effects, state structure, key-based state reset, and pure rendering. Scoped to React itself; not a framework-specific corpus. | Reference | ||
Redis best practicesSource-linked guidance on Redis fundamentals: core data types, key expiration, RDB and AOF persistence, maxmemory eviction policies, and pipelining. Scoped to Redis Open Source as documented at redis.io; not a client-library or Redis Cloud operations corpus. | Reference | ||
Rust best practicesSource-linked guidance on Rust fundamentals from The Rust Book: ownership and borrowing, error handling with Result, pattern matching, iterators and closures, and packages, crates, and modules. Scoped to Rust; not a general programming corpus. | Reference | ||
Self-hosted AI referenceSource-linked operating notes for running your own model server, Next.js app, Postgres, and Cloudflare edge. Scoped to Next.js 16 and current vLLM; not a general knowledge corpus. | Reference | ||
Spring Boot best practicesSource-linked guidance on Spring Boot fundamentals: code structure, dependency injection, auto-configuration, externalized configuration, and a first application. Scoped to current Spring Boot. | Reference | ||
SQLite best practicesSource-linked guidance on SQLite fundamentals: WAL mode, query plans, type affinity, foreign key enforcement, and online backup. Scoped to SQLite; not a general SQL or relational-database corpus. | Reference | ||
Svelte best practicesSource-linked guidance on Svelte 5 fundamentals: reactive state with $state, derived values, effects, component props, and event handling. Scoped to Svelte 5; not a SvelteKit or legacy Svelte 4 corpus. | Reference | ||
SwiftUI best practicesSource-linked guidance on SwiftUI fundamentals: views and view composition, state and data flow, layouts and stacks, navigation, and previews and testing. Scoped to current SwiftUI docs. | Reference | ||
Tailwind CSS best practicesSource-linked guidance on Tailwind CSS v4 fundamentals: Vite installation, utility-first styling, theme variables, automatic content detection, and responsive breakpoints. Scoped to Tailwind CSS v4; not a general CSS corpus. | Reference | ||
Terraform best practicesSource-linked guidance on Terraform core workflows: state and remote backends, modules, variables and outputs, plan and apply, and resource dependencies. Scoped to Terraform language and CLI fundamentals; not a provider-specific corpus. | Reference | ||
TypeScript best practicesSource-linked guidance on TypeScript fundamentals: strict-mode compiler options, safer index access, type narrowing, the satisfies operator, and preferring unknown over any. Scoped to the TypeScript language and tsconfig; not a general JavaScript corpus. | Reference | ||
Vite best practicesSource-linked guidance on Vite fundamentals: the dev server and HMR, static assets, production builds, env variables and modes, and performance. Scoped to Vite; not a general bundler corpus. | Reference | ||
Vitest best practicesSource-linked guidance on Vitest fundamentals: writing and organizing tests, mocking, code coverage, snapshot testing, and watch-mode filtering. Scoped to Vitest as documented at vitest.dev; not a general JavaScript testing corpus. | Reference | ||
Vue best practicesSource-linked guidance on Vue 3 fundamentals: reactivity, components and props, the Composition API, computed properties and watchers, and lifecycle hooks. Scoped to Vue 3; not a Vue 2 migration corpus. | Reference | ||
Web accessibility best practicesSource-linked guidance on web accessibility fundamentals: semantic HTML, the first rule of ARIA, keyboard operability, color contrast, and form labels. Scoped to web accessibility; not a WCAG conformance checklist. | Reference | ||
Web security best practicesSource-linked guidance on core web security controls: HTTPS enforcement with HSTS, Content Security Policy, cookie attributes, XSS prevention, and CORS. Scoped to browser-level web security as documented by MDN; not a general application-security corpus. | Reference | ||
CODATA fundamental physical constantsCODATA 2022 recommended values of the fundamental physical constants, published by NIST (a US government work). One document per constant citing the NIST complete listing; refreshed on each CODATA release, roughly every four years. | Official | ||
DNS parameters (IANA registry)Assigned Domain Name System (DNS) parameters from the IANA DNS Parameters registry: resource record (RR) TYPEs, RCODEs, CLASSes, and OpCodes, one document per assigned value with its meaning, references, and template or registration date where the registry lists them. Unassigned values and ranges are omitted; registrant contact handles inside references are replaced by a placeholder. | Official | ||
HTTP field names (IANA registry)Registered HTTP field (header and trailer) names from the IANA Hypertext Transfer Protocol (HTTP) Field Name Registry, one document per name with its status, structured type, and defining reference. | Official | ||
HTTP methods (IANA registry)Registered HTTP methods from the IANA Hypertext Transfer Protocol (HTTP) Method Registry, one document per method with its safe and idempotent flags and defining reference. | Official | ||
HTTP status codes (IANA registry)Assigned HTTP status codes from the IANA Hypertext Transfer Protocol (HTTP) Status Code Registry, one document per code with its reason phrase, class, and defining reference. | Official | ||
IANA application/* media types (standards tree)IANA-registered application/* media types, standards-tree partition (every subtype not starting with vnd.; prs. and x- included). One document per media type with its registry status note, published references (RFCs, standards, URLs, and registering organisations; individual contact names omitted), and its registration-template URL. | Official | ||
ISO 4217 currency codes (SIX Group)ISO 4217 currency codes from the maintenance agency SIX Group: one document per alphabetic code from List One (178 current codes, published 2026-09-17) and List Three (137 historic codes, published 2026-01-01), with numeric code, minor units, every entity using the code, and withdrawal records for historic codes. | Official | ||
ISO 639-2 language codes (Library of Congress)Language codes from the ISO 639-2 code list of the Library of Congress, the ISO 639-2 Registration Authority: one document per language with its bibliographic (B) code, terminologic (T) code where it differs, ISO 639-1 code where assigned, and the English and French names. | Official | ||
Link relation types (IANA registry)Registered link relation types from the IANA Link Relations registry, one document per relation with its description, defining reference, and registry notes. | Official | ||
MCP server directoryEvery published server in the Koskamo MCP directory: endpoint, transport, sign-in model, tools, and documentation, live-checked weekly. | Directory | ||
Media types (IANA registry)Registered media types (MIME types) in the audio, font, haptics, image, message, model, multipart, text, video top-level types of the IANA Media Types registry, one document per type with its subtype, defining references, and any deprecation or obsoletion marker. References that name an individual are withheld as personal data. The application top-level type is covered separately. | Official | ||
Periodic table of the elementsProperties of all 118 chemical elements from the PubChem periodic table, published by NCBI at the US National Institutes of Health (a US government work). One document per element citing its PubChem element page; group and period numbers come from PubChem's element annotations. | Official | ||
Planetary fact sheet (NASA)Physical and orbital data for the planets, the Moon, and Pluto from the NASA NSSDCA Planetary Fact Sheet (metric), a US government work. One document per body with every table row as NASA states it, including footnotes. | Official | ||
Planetary satellites (NASA/JPL)Physical parameters and mean orbital elements for the planetary satellites tabulated by NASA/JPL Solar System Dynamics, one document per satellite: GM, mean radius, and mean density with uncertainties where measured, plus mean orbital elements (semi-major axis, eccentricity, inclination, period, precession periods) with units as published. | Official | ||
SI units and prefixes (BIPM SI Reference Point)The 7 SI base units, 22 named SI derived units, and 24 SI prefixes from the BIPM SI Reference Point (the authoritative digital reference of the SI Digital Framework, CC BY 3.0 IGO). One document per unit or prefix: base units carry the current definition with its defining constant and superseded definitions, derived units the expression in base and other SI units, and prefixes the exponent and scaling factor. | Official | ||
SPDX License ListThe SPDX License List version 3.29.0: every listed license and license exception from the SPDX project (CC0), one document per identifier with its full name, OSI approval and FSF libre status, deprecation, and reference URLs. Full license texts are not included. | Official | ||
Time zones (IANA Time Zone Database)Canonical time zones from the IANA Time Zone Database release 2026e (2026-09-29 17:14:38 -0700) (public domain), one document per zone1970.tab zone with its countries, principal-location coordinates, selection comment, and backward-compatible link names. | Official | ||
TLS cipher suites (IANA registry)Assigned TLS cipher suites from the IANA TLS Cipher Suites registry, one document per assigned value with its DTLS-OK flag, Recommended status (Y = recommended, N = not recommended, D = discouraged), defining references, and any registry comment. | Official | ||
UN M49 country and area codes (UN Statistics Division)Standard country or area codes for statistical use (M49) from the UN Statistics Division: one document per country or area with its M49 code, ISO alpha-2/alpha-3 codes, region hierarchy, and LDC/LLDC/SIDS flags, plus one document per global region, region, sub-region, and intermediate region listing its members. | Official | ||
URI schemes (IANA registry)Registered URI schemes from the IANA Uniform Resource Identifier (URI) Schemes registry, one document per scheme with its description, registration status (Permanent, Provisional, or Historical), CRI scheme number, well-known URI support, registration template, and citable references. References that name individuals are omitted. | Official | ||
Vendor media types N-Z (IANA registry)Assigned vendor-tree (vnd.) application media types from the IANA Media Types registry whose subtype begins with N-Z (case-insensitive) or a non-alphanumeric character, one document per type with its template page, defining references, registering organizations, and obsolescence notes. Individual contact persons named in the registry are omitted. | Official | ||
Vendor media types, 0-9 and A-M (IANA registry)Vendor (vnd.*) media types from the IANA Media Types registry whose subtype begins with 0-9 or a-m, one document per type with its registration template, registry note, and non-personal references (personal change-controller names omitted). | Official | ||
Well-known ports (IANA registry)IANA System Ports (0–1023) from the IANA Service Name and Transport Protocol Port Number Registry, one document per port with an assigned service name. Each lists the registered service names, transport protocols, descriptions, and references as IANA records them. | Official |