OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Prismic’s Content API returns document data at a selected repository ref. A ref identifies a published, draft or scheduled content version.
Prismic Content API queries ↗
ref, predicates, language, pageSize and page · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Fetch the repository ref, then traverse document queries with page and pageSize under that same ref and language.
Prismic Content API queries ↗
ref, predicates, language, pageSize and page · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Predicates, field selection, ordering and language control the document result set. Relationship expansion and integration-field refs require explicit selection.
Prismic Content API queries ↗
ref, predicates, language, pageSize and page · Checked 2026-10-22
Access cost barrier -
-
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
Prismic Content API queries ↗
ref, predicates, language, pageSize and page · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Public repositories can be queried without a secret token. Private repositories require an access_token from repository settings; the ref is a content-version selector, not authorization.
Prismic Content API queries ↗
access_token and ref (required) · Checked 2026-10-22
Downstream permission -
-
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
Prismic Content API queries ↗
access_token and ref (required) · Checked 2026-10-22
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 0.0/10
Assessed route is expressly read-only
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
The assessed Content API query route reads documents. Migration API writes are a separate interface and are not credited here.
Prismic Content API queries ↗
Content query endpoint · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
Prismic Content API queries ↗
access_token and ref (required) · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
Prismic Content API queries ↗
ref, predicates, language, pageSize and page · Checked 2026-10-22
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Uncached Content API requests are limited to 200/second, with 2,048-character URLs. The official client retries a rate-limited query after one second.
Prismic Content API queries ↗
Limits · Checked 2026-10-22
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.
Prismic Content API queries ↗
ref, predicates, language, pageSize and page · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.
Prismic Content API queries ↗
ref, predicates, language, pageSize and page · Checked 2026-10-22
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
Prismic Content API queries ↗
ref, predicates, language, pageSize and page · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
Prismic Content API queries ↗
access_token and ref (required) · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Retain selected document JSON with language and ref context. Renderers, custom-type definitions, assets and complete version history need separate handling.
Prismic Content API queries ↗
ref, predicates, language, pageSize and page · Checked 2026-10-22
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
Prismic Content API queries ↗
access_token and ref (required) · Checked 2026-10-22
Rights to custom logic -
-
Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
Prismic Content API queries ↗
access_token and ref (required) · Checked 2026-10-22
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Public repositories can be queried without a secret token. Private repositories require an access_token from repository settings; the ref is a content-version selector, not authorization.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Fetch the repository ref, then traverse document queries with page and pageSize under that same ref and language. Predicates, field selection, ordering and language control the document result set. Relationship expansion and integration-field refs require explicit selection.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| REST Content API document queries for a selected repository ref and language | access token | Customer | No | Customer-supplied credentials | 2026-10-22 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Minimum plan and exact route fees remain unconfirmed.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The assessed Content API query route reads documents. Migration API writes are a separate interface and are not credited here.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established. | Prismic Content API queries ↗ref, predicates, language, pageSize and pageChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified. | Prismic Content API queries ↗ref, predicates, language, pageSize and pageChecked 2026-10-22 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Retain selected document JSON with language and ref context. Renderers, custom-type definitions, assets and complete version history need separate handling.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can write external integration code. Native workflow rights and independent execution remain unresolved (record access does not establish portable application logic).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopePrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Prismic’s Content API returns document data at a selected repository ref. A ref identifies a published, draft or scheduled content version. | Prismic Content API queries ↗ref, predicates, language, pageSize and pageChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Fetch the repository ref, then traverse document queries with page and pageSize under that same ref and language. | Prismic Content API queries ↗ref, predicates, language, pageSize and pageChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Predicates, field selection, ordering and language control the document result set. Relationship expansion and integration-field refs require explicit selection. | Prismic Content API queries ↗ref, predicates, language, pageSize and pageChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Public repositories can be queried without a secret token. Private repositories require an access_token from repository settings; the ref is a content-version selector, not authorization. | Prismic Content API queries ↗access_token and ref (required)Checked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | Prismic Content API queries ↗ref, predicates, language, pageSize and pageChecked 2026-10-22 |
| Which external write operations are documented? | Assessed route is expressly read-onlyPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. The assessed Content API query route reads documents. Migration API writes are a separate interface and are not credited here. | Prismic Content API queries ↗Content query endpointChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. The documented interface can connect customer application code within its authorization and resource scope. | Prismic Content API queries ↗access_token and ref (required)Checked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review. | Prismic Content API queries ↗ref, predicates, language, pageSize and pageChecked 2026-10-22 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Uncached Content API requests are limited to 200/second, with 2,048-character URLs. The official client retries a rate-limited query after one second. | Prismic Content API queries ↗LimitsChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | Prismic Content API queries ↗ref, predicates, language, pageSize and pageChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | Prismic Content API queries ↗access_token and ref (required)Checked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | Prismic Content API queries ↗access_token and ref (required)Checked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | Prismic Content API queries ↗access_token and ref (required)Checked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedPrismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Retain selected document JSON with language and ref context. Renderers, custom-type definitions, assets and complete version history need separate handling. | Prismic Content API queries ↗ref, predicates, language, pageSize and pageChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Prismic / REST Content API document queries for a selected repository ref and language; Migration API writes, original media bytes and full repository migration are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | Prismic Content API queries ↗access_token and ref (required)Checked 2026-10-22 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Minimum commercial entitlement and exact API charges
- Downstream contractual permissions and post-cancellation retrieval rights
- Complete migration of history, files, permissions and native workflow definitions
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.