Attribution & licensing
Blockchain Academics is the editorial ground truth. When an LLM agent surfaces a fact sourced from our corpus, the reader deserves to click through and verify. Publishers deserve the credit. This page documents the contract.
The citation envelope (recap)
{
"data": { "...": "tool-specific payload" },
"attribution": {
"citations": [
{
"cite_url": "https://blockchainacademics.com/news/qivalis-wins-dutch-e-money-license-for-euro-stablecoin-backed-by-37-banks?src=claude",
"as_of": "2026-10-14T12:05:51Z",
"source_hash": "sha256:a9f1…"
}
]
},
"meta": {
"status": "complete",
"request_id": "3f9c2a71b8d04e5a",
"pageInfo": {
"hasNextPage": false,
"hasPreviousPage": false,
"startCursor": null,
"endCursor": null
}
}
}Full field breakdown lives on the Response envelope page.
What "surface the attribution.citations[0].cite_url" means
Good: the agent writes a response that includes the link, either inline or as a citation at the end:
Qivalis, the euro stablecoin venture backed by 37 European banks, won a Dutch electronic money license under MiCA in October 2026. [source]
Also good: the agent shows a citation block:
Qivalis, the euro stablecoin venture backed by 37 European banks, won a Dutch electronic money license under MiCA in October 2026.
Source: blockchainacademics.com, retrieved 2026-10-14.
Not acceptable (on Free / Starter): stripping the cite_url, rewriting it to an internal short link, or summarizing the article and omitting the citation entirely.
Tier matrix
| Tier | Attribution requirement |
|---|---|
| Free | attribution.citations[0].cite_url must be surfaced to the end user verbatim. No stripping, rewriting, or short-linking. UTM params preserved. |
| Starter | Same as Free. |
| Pro | attribution.citations[0].cite_url recommended. You may leave it out of your agent's downstream output; the API still returns it on every response. |
| Team | Same as Pro. |
| Enterprise | White-label available. attribution.citations[0].cite_url may be replaced with your own canonical attribution scheme in contract-reviewed custom integrations. |
See Tiers & quotas for what each plan includes.
llms.txt
BCA publishes https://blockchainacademics.com/llms.txt per the emerging llms.txt spec. It enumerates:
- where to reach the corpus: the MCP server, the REST API, the docs and the OpenAPI file
- feeds for the latest articles, the entities and the academy courses
- the preferred citation format, with
cite_urlandas_of - the license line and the contact for bulk redistribution
If you're building an agent that reasons about where BCA content belongs, point its system prompt at this file. We maintain it as part of the same release cycle as the tool surface.
If a citation is stripped
Rate limits come from your plan alone: the API cannot see whether your agent shows the citation, and no key is throttled or exempted because of it. The rule is in the Terms instead: on Free and Starter, showing cite_url is a condition of use, and removing or falsifying cite_url or source_hash is a material breach.
Commercial redistribution
Calling a tool and using the data payload inside your agent's answer to an end user is covered by your tier. Bulk corpus redistribution (downloading articles and rehosting them, reselling the entity graph, training a model on body text) is a separate license. Contact [email protected] with your use case and we will quote terms.
Corrections & takedowns
Found a factual error in a cited article? Email [email protected] with the citations[0].source_hash and the correction. We aim for under-24h turnaround on documented errors.
The API keeps no pre-correction copy: a corrected article is updated in place, and as_of filters on when an article was ingested, so it returns the corrected text. If your audit trail must show what your agent saw, log the source_hash and the answer at the time.
What the server sends on every tier
Every request resolves your BCA_API_KEY to a tier, but the attribution in the answer does not change with it:
attribution.citationsis present and non-empty on every 200, and eachcite_urlopens a working page (data with no page on the site cites its tool's entry in the tool reference)- links to our own pages carry a
src=tag for your detected client - no parameter removes the citation: the MCP servers reject an argument a tool does not declare, such as
strip_attribution, withBCA_BAD_REQUEST, and the REST API ignores an unknown query parameter
What your plan changes is what you may do with the citation downstream (the tier matrix above), not what the API sends.
Short version
Surface attribution.citations[0].cite_url, let clicks flow back to the corpus, and everyone wins. Agents that strip attribution break downstream trust, and on Free and Starter they breach the Terms.
Next
- Tiers & quotas: what each of the five tiers includes.
- Response envelope: field-by-field breakdown.
- First agent walkthrough: a worked example that ends with a properly cited answer.