Agent Delivery
Package docs status
Section titled “Package docs status”This page is generated from package source documentation in the Capell packages repository and the checked-in manifest. Source documentation is not distribution status. Before running a Composer command, verify that the exact package and compatible 1.x release are available through public Packagist or the authenticated marketplace account.
| Field | Value |
|---|---|
| Composer package | capell-app/agent-delivery |
| Package slug | agent-delivery |
| Product group | Capell AI |
| Tier | premium |
| Bundle | ai |
| Runtime contexts | frontend |
| Capell version | ^1.0 |
| Catalogue role | extension |
| Release channel | Beta |
| Source repository | capell-app/packages |
| Source path | packages/agent-delivery |
| Docs source | packages/agent-delivery/docs |
| Manifest | capell.json |
What This Plugin Adds
Section titled “What This Plugin Adds”Agent Delivery is an Available, No schema impact Capell package in the Capell AI product group. It ships as capell-app/agent-delivery and extends these surfaces: frontend.
Agent Delivery exposes published Capell pages as public JSON discovery, page-manifest, page-index, and semantic-chunk endpoints.
The package adds no admin screen. AI agents and answer engines can read sanitized published-page payloads without admin access or HTML scraping.
Status details:
- Status: Available
- Tier: premium
- Bundle: ai
- Composer package:
capell-app/agent-delivery - Namespace:
Capell\AgentDelivery - Theme key: not applicable
Why It Matters
Section titled “Why It Matters”For developers: Package contracts let contributors add metadata, references, related URLs, access policy, and chunks while Actions keep the HTTP controllers thin.
For teams: Published content becomes available to machine readers through stable page and chunk responses while unpublished and admin data stay outside the public contract.
Screens And Workflow
Section titled “Screens And Workflow”Screenshot contract: docs/screenshots.json.




- Public page manifest JSON response (frontend, required evidence).
- Public page chunks JSON response (frontend, required evidence).
Technical Shape
Section titled “Technical Shape”Service providers
Section titled “Service providers”Capell\AgentDelivery\Providers\AgentDeliveryServiceProvider
Config files
Section titled “Config files”packages/agent-delivery/config/capell-agent-delivery.php
Route files
Section titled “Route files”packages/agent-delivery/routes/agent-delivery.php
Extension contracts
Section titled “Extension contracts”AgentDeliveryAccessPolicyContributorAgentDeliveryChunkContributorAgentDeliveryContributorAgentDeliveryMetadataContributorAgentDeliveryReferenceContributorAgentDeliveryRelatedUrlContributor
Actions
Section titled “Actions”AnalyzeAgentDeliveryChunkBudgetActionBuildAgentDeliveryChunksActionBuildAgentDeliveryDiscoveryPayloadActionBuildAgentDeliveryPageActionBuildAgentDeliveryPageIndexActionResolveAgentDeliveryPageAction
Data objects
Section titled “Data objects”AgentDeliveryChunkBudgetDataAgentDeliveryChunkDataAgentDeliveryPageDataAgentDeliveryPageIndexEntryDataResolvedAgentDeliveryPageData
Manifest contributions
Section titled “Manifest contributions”agent-capability: Capell\AgentDelivery\Manifest\AgentDeliveryContractsContributionhealth-check: Capell\AgentDelivery\Health\AgentDeliveryHealthCheckroute: Capell\AgentDelivery\Manifest\AgentDeliveryRoutesContribution
Health checks
Section titled “Health checks”Capell\AgentDelivery\Health\AgentDeliveryHealthCheck
Cache tags
Section titled “Cache tags”agent-delivery
Data Model
Section titled “Data Model”This package has no schema impact. It extends Capell through agent-capability contributions, health-check contributions, and route contributions instead of declaring package-owned tables.
Install Impact
Section titled “Install Impact”- Required packages:
capell-app/core,capell-app/discovery-foundation. - Admin navigation: no admin page or resource contribution is declared.
- Admin/editor extensions: none declared.
- Permissions: no package permission declarations or Shield gates detected; host access rules still apply.
- Public routes: loads
routes/agent-delivery.php; registersAgentDeliveryRoutesContribution. - Database changes: no package migrations declared.
- Config:
config/capell-agent-delivery.php. - Settings: no package settings declared.
- Queues or schedules: none declared.
- Cache tags:
agent-delivery. - Commands: none declared.
Common Pitfalls
Section titled “Common Pitfalls”- Keep required Capell packages on compatible v4 releases:
capell-app/core,capell-app/discovery-foundation. - Review package configuration before production-like verification:
config/capell-agent-delivery.php. - Review middleware, throttling, signatures, and public-output safety in
routes/agent-delivery.phpbefore exposing routes. - Keep public Blade and cached HTML free of authoring markers, model IDs, permissions, signed editor URLs, and lazy database queries.
- Custom write integrations must preserve invalidation for
agent-deliverycache tags.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Likely cause | Check | Fix |
|---|---|---|---|
| Package surface is missing after install | Provider or manifest is not loaded | Confirm capell.json, package composer.json, and provider registration | Reinstall the package, refresh Composer autoload, and clear host caches |
| Route returns unexpected output | Route cache, middleware, or signed URL setup does not match the package route file | Check the route files listed in Technical Shape | Clear route cache and verify middleware before exposing public routes |
| Public output leaks unexpected state | Render data, cache variation, or authoring boundary has regressed | Check public Blade, cache tags, and public-output safety tests | Move data loading out of Blade and rerun the package public-output tests |
Quick Start
Section titled “Quick Start”- Install the package:
composer require capell-app/agent-delivery. - Open
/api/capell/agent/v1/pages/manifest?url=/and confirm the public output renders without admin state.
Next Steps
Section titled “Next Steps”- Package docs
- Overview
- Worked extension examples
- Configuration files:
config/capell-agent-delivery.php. - Troubleshooting
- Screenshot contract
- Marketplace assets
- Capell content language plan
- Capell documentation design system
- Capell and package ERD notes
- Related packages: Discovery Foundation, Site Discovery.