researchoutputs.ai valid
researchoutputs.ai
researchoutputs.ai is a registry for everything a research project produces.
- Authority
- 46 reach 0 · trust 6 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://researchoutputs.ai/llms.txt
- llms-full.txt
- https://researchoutputs.ai/llms-full.txt
- Sections
- 5
- Links
- 17
- Size
- 4855 bytes
- Registered
- 2026-06-03
- Country
- Germany Hosting inference
- Hosting country
- Germany Hosting inference
- Country evidence
- No published address evidence collected yet
- Categories
- AI and machine learning
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T18:43:33.394Z
- Last checked
- 2026-10-27T18:43:34.561Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T18:43:33.398Z. Cached copy · Source on researchoutputs.ai
# researchoutputs.ai
> researchoutputs.ai is a registry for everything a research project produces.
> A grant's datasets, code, models, protocols, and publications each get a
> versioned, citable record — FAIR-checked on deposit, linked to the grant that
> funded it, and rolled up to the institution, funder, and researcher behind it.
> Records are public and machine-readable: each carries schema.org JSON-LD and a
> citation, exposes per-output metadata in standard schemas (schema.org,
> DataCite, Dublin Core, BibTeX, CodeMeta, Croissant), and is queryable and
> depositable by AI agents over a Model Context Protocol (MCP) server. Given a
> grant number and funder, the platform also assembles what is already published
> under the award (OpenAlex, DataCite, Crossref, and the full NIH RePORTER
> record for NIH awards) and computes open-access and data-sharing compliance.
## Key pages
- [Home](https://researchoutputs.ai/): what the registry is and how a record is built.
- [Explore](https://researchoutputs.ai/explore): browse and search published Grant Spaces.
- [Create a deposit](https://researchoutputs.ai/new): start a Grant Space from a grant number + funder, or by uploading files.
- [Grant Space](https://researchoutputs.ai/space/): a published record (`/space/<uuid>`) — award metadata, every output with PMID/PMCID/DOI and public-access status, computed funder-compliance, a reuse graph, a citation (text + BibTeX), and schema.org `Collection` JSON-LD with `funding`, `creator`, `sourceOrganization`, and per-output `hasPart` nodes.
- [Researcher](https://researchoutputs.ai/people/): a researcher's published records, keyed by ORCID (`/people/<orcid>`).
- [Institution](https://researchoutputs.ai/institutions/): an institution's portfolio, keyed by ROR (`/institutions/<ror>`).
- [Funder](https://researchoutputs.ai/funders/): a funder's portfolio, keyed by ROR (`/funders/<ror>`).
- [Lineage](https://researchoutputs.ai/lineage): the cross-grant lineage graph — which grants' outputs fed later work.
- [Agent & workbench connector](https://researchoutputs.ai/connect): how to connect an agent to the MCP server and deposit outputs.
## Agent access (MCP)
Model Context Protocol server (streamable HTTP, JSON-RPC over POST). Machine-readable manifest: [/.well-known/mcp.json](https://researchoutputs.ai/.well-known/mcp.json).
- Endpoint: `https://ldhooktwashovvmygqly.supabase.co/functions/v1/mcp`
- Scope to one grant by appending `?space=<space-uuid>`.
- Every request needs the project's public `apikey` header (shown, ready to copy, at [/connect](https://researchoutputs.ai/connect)). Read tools need no user token; `deposit_output` needs an `Authorization: Bearer ros_…` token, issued after a one-time human ORCID sign-in and then fully agent-usable.
Tools: `search_spaces(query, limit)`, `get_space(space_id)`, `get_citation(space_id, format)`, `get_reuse(space_id, limit)`, `check_compliance(space_id)`, and `deposit_output(space_id, …)` (token required — deposits l
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| ivankotov.eu | Ivan Kotov — public scientific corpus | documentation | US | 45 | ✓ | ✓ | |
| wovepaper.com | wovepaper | interface Science and research APIs and SDKs | NL | 51 | ✓ | ||
| scispace.com | SciSpace - Your AI Research Assistant | documentation AI and machine learning Science and research | — | 58 | ✓ | ✓ | |
| opensource.legal | cite | interface AI and machine learning Developer tools +2 | — | 48 | ✓ | ✓ | |
| digital-science.com | Digital Science | documentation Education Data and analytics +1 | US | 60 | ✓ | ||
| opengrants.io | OpenGrants | interface AI agents and MCP APIs and SDKs +1 | — | 51 | ✓ | ✓ | |
| gptr.dev | GPT Researcher | interface Science and research Education +3 | DE | 55 | ✓ | ✓ | |
| supraworx.com | SupraWorx | transactional | DE | 50 | ✓ |
Machine-readable: GET /v1/resolve?q=researchoutputs.ai · GET /v1/domain/researchoutputs.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage researchoutputs.ai, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for researchoutputs.ai:
1. POST https://agentwebmap.com/v1/sites/researchoutputs.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://researchoutputs.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/researchoutputs.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/researchoutputs.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.