search_archive
Search the ISHOB archive (titles, keywords, authors). All words must match.
{"query": "laser calibration", "limit": 10}
A growing machine-readable archive of structured knowledge, organized for automated discovery, retrieval, analysis, and AI applications.
Built for machines. Understandable by people.
ISHOB continuously organizes and prepares structured knowledge for automated systems. Figures are read live from the archive index.
Every record: JSON · stable identifier · versioned · license & rights metadata included
ISHOB runs a remote Model Context Protocol server at api.ishob.com/mcp. Assistants and agents connect once and get 3 free discovery tools plus paid content tools. Paid tools settle per call with x402 inside the MCP request: no account, no API key, no subscription.
search_archiveSearch the ISHOB archive (titles, keywords, authors). All words must match.
{"query": "laser calibration", "limit": 10}
list_topicsList knowledge topics with live resource counts.
{}
get_catalog_pageBrowse the catalog, 100 resources per page, optionally by topic.
{"page": 0, "topic": "laser-calibration"}
get_documentRecord metadata, abstract, license and attribution for one resource.
{"id": "<resource id>"}
get_fulltextStructured full text (sections) of one resource, with license.
{"id": "<resource id>"}
get_referencesParsed reference list of one resource.
{"id": "<resource id>"}
extract_webpageFetch a public web page live (robots.txt respected) and return clean Markdown. Not stored or redistributed.
{"url": "https://example.org/article"}
search_specsFull-text search over abstracts and full texts, with extracted technical specifications (values, ranges, tolerances, units). Numeric constraints like "50 Nm" are matched.
{"query": "torque sensor 50 Nm"}
query_specsStructured specification table filtered by quantity (e.g. accuracy, wavelength, range), unit family, unit and value range, with source document and license.
{"quantity": "wavelength", "unit": "nm", "min": 500, "max": 700}
Point any Streamable-HTTP MCP client at the endpoint. Free tools work immediately. For paid tools, use an x402-capable MCP client (for example the open-source @x402/mcp package): it reads the payment requirement returned by the tool, signs a USDC payment and retries the call automatically.
Server card: /.well-known/mcp.json. The same capabilities over plain HTTPS are listed in the API section.
{
"mcpServers": {
"ishob": {
"type": "http",
"url": "https://api.ishob.com/mcp"
}
}
}
The spec tools read the structured full texts and pull out measurable facts: values, ranges (“4–20 mA”), tolerances (“±0.1 %”) and their units, normalised to SI and labelled with the quantity they describe (accuracy, range, wavelength, torque…). Agents can ask for “torque sensor 50 Nm” or for every wavelength between 500 and 700 nm, and each answer cites its source record and license.
ISHOB is an automated pipeline, not a static dump. These are the stages every resource passes through before an agent can retrieve it.
No sign-up, no API keys. A wallet-capable client is all an agent needs for paid calls.
Fractions of a cent per request. Missing resources return 404 before any payment is asked; failed deliveries are never charged.
Licenses travel with every record. Live web extraction honours robots.txt and is never stored or redistributed.
MCP server card, OpenAPI, llms.txt, ai-data.json, sitemaps and the x402 Bazaar describe every capability.
ISHOB is designed to be discovered and accessed programmatically. AI agents and automated systems can explore available topics, inspect structured metadata, search the archive, and request available resources through machine-readable interfaces.
robots.txt, sitemaps, /.well-known/ai-data.json, /.well-known/mcp.json, llms.txt and OpenAPI describe the archive.
Plain HTTPS or MCP. No accounts, no API keys, no browser workflow.
Consistent JSON records with stable identifiers, sections, references and rights fields.
Catalog, topics and search are free; eligible content is served per request.
Resources are organized into knowledge topics. Each topic is a machine-readable collection with its own catalog and search scope.
ISHOB organizes knowledge into consistent, machine-readable records designed for automated discovery, retrieval, analysis, and AI workflows.
Full records add the abstract, structured sections, references, and complete license, attribution and provenance fields. Data & rights.
// EXAMPLE RECORD — illustrative values, real field structure { "id": "doi-1a2b3c4d5e6f7a8b9c0d", "title": "Example resource", "year": 2025, "topics": ["example-topic"], "keywords": ["measurement", "uncertainty"], "license": "CC-BY-4.0", "has_fulltext": true, "has_references": true, "access": "paid", "content_endpoint": "/api/document/doi-1a2b3c4d5e6f7a8b9c0d", "fulltext_endpoint": "/api/document/doi-1a2b3c4d5e6f7a8b9c0d/fulltext" }
Structured resources are organized for automated discovery and programmatic access. Explore the archive, inspect available metadata, and retrieve resources through the ISHOB API, or run the same steps as MCP tool calls (list_topics → search_archive → get_fulltext).
/.well-known/ai-data.json/api/topics/api/search?q=…/api/document/{id}/api/document/{id}/fulltextDiscovery is free. Eligible resources are delivered per request using the x402 HTTP payment protocol: compatible clients receive a machine-readable payment requirement and complete it programmatically.
Over MCP the same exchange happens inside the tool call: the tool returns the payment terms, the client signs, and the result arrives with a settlement receipt. Network: Base · settled in USDC. Missing resources return 404 before any payment is requested; failed deliveries are not charged. Clients without x402 support can still use all free endpoints.
GET /api/document/{id}/fulltextPAYMENT-REQUIRED termsISHOB is a continuously expanding archive of structured knowledge prepared for machine discovery and AI consumption. Resources are published only when their reuse rights are verified, and each record keeps its license, attribution and provenance metadata.
The figures on this page are the archive's actual current contents. Discovery data is free; some resources are delivered through paid machine access.
Start here: /api → /api/catalog → /api/topics → /api/search