Skip to main content
Capell home
Live demo
Released

Agent Delivery

Make published pages readable through public JSON endpoints.

Version
1.1.9
Released
10 November 2026
Requires
Discovery Foundation
Licence
Commercial

Price £39.00

Check access and installation
Public Agent Delivery page manifest JSON for a published Capell page
A stable public page manifest gives agents structured content without exposing admin data.

Check your application before checkout

Outcome

What it solves

The problem

Machine readers cannot reliably access published site content in structured form.

What your site gets

Published pages are available to machine readers as structured responses.

Questions buyers ask

Which pages can machine readers access?
The public responses expose published pages; unpublished and admin data stay outside the contract.
What format do agents receive?
Published pages are available as JSON discovery, manifests, indexes and semantic chunks.
Does this add an admin screen?
The package adds no admin screen.
Usage

Use it in your project

Use this package when another service needs published page content in smaller, reusable sections. Drafts and private editing data stay outside the public response.

Picture it on your site

If a service needs to read a product guide, decide which published pages it should consume and which chunks it actually needs. Compare a response with the public page before integrating it. This gives the integration a defined content source; it does not guarantee how an external search or AI service will use that information.

2 captures

Included

Connect content to your website

  • Expose page discovery, indexes and manifests.
  • Deliver published content as semantic chunks.

Is this right for your project?

Choose the delivery boundary

Decide whether your application needs rendered pages, a separate frontend or another service reading published content. A delivery package is useful when it makes that boundary explicit instead of asking another system to understand private editing state. Your Laravel application still owns its routes, presentation and access decisions; the published contract is what a consuming frontend should build against.

Check a real consuming application

Test one published page from end to end, including its layout, language, missing-content response and links to other pages. Compare that with an unpublished page so you can see the boundary working. Plan how the consuming application refreshes content after a change, rather than assuming that an endpoint or successful response also solves caching and deployment.

Licence £39.00 / 12 months

One customer organisation; up to 5 named users. Each entitlement covers one production website or application and up to two non-production environments, with a maximum of three active installations.

12 months of protected downloads, updates and included standard support.

+ VAT where applicable

You may ask Capell for a full refund within 14 days of purchase. Requests are assessed case by case against the recorded order, access and support history. This applies to live paid first-party packages; third-party author sales have separate terms. Read the Refund Policy

Renewal is charged at the price current when you renew. The price is shown before you pay.

Sign in to buy licence
Review site impact

Marketplace listings can describe install impact and data access.

This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.

Paid checkout adds access to the purchasing account after payment. Review compatibility and site impact, then follow the installation steps for this package.

Open the Capell demo

This listing has no page of its own in the demo. Open the demo to see Capell running.

Installation impact

Before you install

Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.

Admin and public surfaces
The package declares: frontend integration, public routes. Review the release documentation for configuration and exposure in your application.
Data and migrations
The manifest declares no package migrations. This does not establish that installation or runtime operations make no data changes. May connect configured Capell content, media, or integration metadata to the named service boundaries for this package.
Background work
A complete jobs and scheduler assessment is not available here. Confirm background processing and worker requirements with the publisher.
Access controls
Access-control changes are not described here. Confirm the required roles and grants with the publisher.
Removal and retained data
A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with the publisher before removal.
  1. 01

    Prepare protected Composer access

    Sign in to the account with active package access. Open its generated installation instructions and configure the protected Composer repository before running the commands below. Keep access credentials private. Open my package installation instructions

  2. 02

    Require the package

    composer require capell-app/agent-delivery
  3. 03

    Install the extension

    php artisan capell:extension-install capell-app/agent-delivery
  4. 04

    Activate the package licence

    In this site’s Admin, open Marketplace, find Agent Delivery (capell-app/agent-delivery), and activate its licence using the purchase licence key if requested. This activates the package you have already installed. Wait for the Marketplace operation to succeed before continuing; keep its queue worker running.

  5. 05

    Report the installed package

    php artisan capell:marketplace:heartbeat
Release and review evidence
Maintenance

Release activity stays visible

These dates come from approved package releases, so you can see the release trail before installing.

Latest approved release
v1.1.9 Nov 10, 2026
Recent activity
13 approved releases in the last 12 months
Capell reviewed

Review evidence for this release

Agent-facing content delivery package reviewed: its read-only endpoints serve published pages only, with caching headers and no exposure of unpublished content.

Review reduces risk, but it is not a permanent security guarantee.

Automated checks passed
AI-assisted analysis completed
Human sign-off completed
Reviewed version
1.1.9
Approval date
Nov 8, 2026

Areas reviewed

  • Strict, maintainable PHP
  • Presentation-only public views
  • Actions and typed boundaries
  • Clean anonymous public output
  • Authorisation and input safety
  • Declared package boundaries
  • Manifest and migration integrity
  • Compatibility and interoperability
  • Meaningful behavioural tests
  • Security and supply-chain checks
  • Performance and operational behaviour
  • Theme delivery quality where applicable
  • Marketplace claims matched to behaviour
  • AI-assisted analysis with human accountability

Accepted limitations

  • The delivery endpoints are intentionally public and unauthenticated by default; sites that want them gated must add their own auth middleware through configuration.
Read the full Capell review method

Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.

Changelog

Release notes and maintenance evidence

Version history

Showing the 10 most recent of 13 approved releases
  1. v1.1.9
    Nov 10, 2026
    Release notes

    Full Changelog: https://github.com/capell-app/agent-delivery/compare/v1.1.8...v1.1.9

  2. v1.1.8
    Nov 2, 2026
  3. v1.1.7
    Oct 28, 2026
  4. v1.1.6
    Oct 20, 2026
  5. v1.1.5
    Oct 17, 2026
  6. v1.1.3
    Oct 9, 2026
  7. v1.1.2
    Oct 8, 2026
  8. v1.1.1
    Oct 8, 2026
  9. v1.1.0
    Oct 7, 2026
  10. v1.1.0-beta.41
    Oct 4, 2026

Before checkout

Know who owns access and what happens next

Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.

Who processes the payment and taxes?

Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.

Which account owns the licence?

The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.

How does the site receive package access?

The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.

What happens if checkout is cancelled or expires?

No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.

How do I request a refund?

There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy

What should I do if access does not appear?

Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.

Capture date and release are not supplied in this gallery. Check the current package listing for scope and compatibility.

Agent Delivery screenshot gallery

Public Agent Delivery page manifest JSON for a published Capell page