From sources to reusable facts

Four-stage pipeline#

When converting public pages into reusable records, Reuseio follows four stages: discovery, structuring, verification, and publication.

01 / DiscoverStart with official product pages, documentation, READMEs, and API references.

02 / StructureExtract product names, providers, capabilities, tags, integrations, and facts.

03 / VerifyBind fields to sources and excerpts, rejecting claims without supporting evidence.

04 / PublishGenerate a consistent Product, Manifest, source chain, and Agent Prompt.

What is a Manifest?#

Manifest is the machine-friendly representation of a Product. It contains descriptions, capabilities, integrations, facts, relationships, sources, and implementation constraints so the web UI, SDK, API, and Agent read the same structure.

const manifest = await registry.getManifest('cloudflare-r2')
const sources = await registry.getSources('cloudflare-r2')
const prompt = await registry.getAiPrompt('cloudflare-r2')

The shared contract#

The web UI, MCP, SDK, REST API, and Agent Skill are different access paths, but they should not maintain conflicting facts. They share the concepts of Product, Capability, Integration, Source, and Evidence, so callers can move between entry points without learning a different data model.

Human readingThe page provides context, explanations, and official links.

Machine readingManifest and JSON preserve structured fields for programs.

Agent decisionsThe Skill connects requirements, capabilities, evidence, and decisions into an auditable chain, while MCP provides the tool-call transport.

How search works#

Search fields include Product Name, Product Alias, Provider Name, Summary, Capability, and Tag. English queries can use PostgreSQL full-text search, while Chinese queries are supplemented by reliable substring matching.

Results are primarily ranked by database relevance, without unexplained manual scores. A search result is a candidate set, not a final recommendation.

Quality checks#

Professional results are not judged by match count alone. Check whether facts are traceable, fields are complete, sources are close to the product behavior, and the conclusion separates verified points from items that still need confirmation.

Do not conflateHigh relevance is not the same as strong support; having a product record does not mean it meets your runtime constraints; lack of evidence does not mean the product lacks the capability.

How agents use it#

An Agent should identify capabilities first, read candidate Manifests next, and then open official sources to confirm implementation details. Reuseio provides facts and structure; the caller decides against task constraints.

Recommended orderSearch → Manifest → Primary Sources → Evidence → Decision