How To Cite Cunicula
Attribution format, licence terms, and machine-readable endpoints for reusing these records.
Cunicula publishes dated, sourced assessments of 169 privacy and private-finance services. You may cite and quote them with attribution. This page states the exact format, what the licence permits, and where the machine-readable terms live.
Attribution Format
Use this pattern:
Worked example for a real record:
The two dates are different facts and both matter. Reviewed is when Cunicula last assessed the record. Retrieved is when you fetched it. Reporting the retrieval date as the review date overstates how fresh the assessment is.
What The Licence Permits
Cite, quote, and use the records with attribution. Bulk redistribution of the dataset requires licensed access. The terms are identified as LicenseRef-Cunicula-Attribution-1.0.
You may
- Citing individual records and facts.
- Quoting limited excerpts in articles, research, and answer-engine output.
- Linking to canonical Cunicula pages and API endpoints.
- Internal research, diligence, and product evaluation.
You must
- Name Cunicula as the source.
- Link the canonical page or API URL for the record cited.
- State the review date carried by the record.
- Do not present a Cunicula editorial rating as a guarantee or as the citing party's own finding.
You may not
- Redistributing a substantial portion of the dataset as a competing dataset, feed, or export.
- Reselling the records without a licensed agreement.
- Altering evidence labels, risk labels, warnings, or source links when republishing a record.
These are bespoke terms, not Creative Commons. Bulk redistribution of the dataset is not granted here because licensed bulk delivery is a separate agreement; see data and API licensing or write to [email protected].
How Current The Data Is
Records are reviewed on a rolling basis, not on a fixed publication schedule. Read the per-record dates rather than assuming a site-wide freshness date.
lastReviewed: Date the record was last reviewed as a whole.kycLastChecked: Date the KYC posture specifically was last checked.checkedAt: Date an automated availability check last ran.changedAt: Date a tracked field last changed.
For changes rather than full re-reads, use the dated change feed at /api/v1/changes. Responses are cached for 86400 seconds (24 hours). Re-fetch no more than daily; use the change feed for deltas rather than polling the full dataset.
What You Should Not Claim
Privacy and evidence scores are Cunicula editorial signals computed from published factor breakdowns. They are not certifications, audits, or guarantees, and they should not be presented as the citing party’s own finding. Records are point-in-time reviews, not live monitoring of availability, price, or legal status.
Machine-Readable Terms
Every API response carries these terms in its meta block and in a Link: rel="license" header, so an automated consumer receives them with the data.
/api/v1/dataset: dataset descriptor: scope, coverage, freshness, licence, and access limits, including a schema.orgDatasetblock./api/v1/services/lnp2pbotreturns a single record with a ready-madecitationblock./api/v1/openapi.json: the full contract.
The published record shape is versioned as 1.0.0. A major bump means a field was removed or changed meaning; a minor bump means a field was added.
Request Limits
The public tier is unauthenticated at 60 requests/minute. Cache locally for 24 hours rather than re-requesting the dataset. Sustained bulk pulls belong on the licensed tier. Public access allows 60 requests per minute; licensed keys allow 600. Full terms are in the API documentation.
Citing The Dataset As A Whole
When your claim is about the collection rather than one service:
When your claim is about one service, cite that record instead so the review date you carry is the one that actually governs the claim.