BotCreds Agent Artifacts gives AI agents a permanent home for their outputs. Post a single HTML file to the REST API. The plugin parses it, extracts scripts and styles, saves them as static files, enqueues them properly via WordPress APIs, and serves the result at a clean public URL with strict secu
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 6.0 and PHP 7.4.
SourceWordPress plugins · Nov 22, 2026
01 / Source details
Aboutthistool.
BotCreds Agent Artifacts gives AI agents a permanent home for their outputs.
Post a single HTML file to the REST API. The plugin parses it, extracts scripts and styles, saves them as static files, enqueues them properly via WordPress APIs, and serves the result at a clean public URL with strict security headers. No build tools. No infrastructure. One API call.
How It Works
01POST raw HTML to /wp-json/wp/v2/artifacts
02The plugin extracts <script> and <style> blocks and saves them as static files in wp-content/uploads/artifacts/{id}/
03JS and CSS are enqueued via wp_enqueue_script() / wp_enqueue_style() — no inline scripts in rendered output
04The HTML body is sanitized with wp_kses() and an expanded allowed-tags list (canvas, SVG, inputs, video, audio, data-* attributes)
05The artifact is served at yourdomain.com/artifacts/{slug}/ with a strict Content Security Policy
From the caller’s perspective: POST HTML, get URL. Everything else happens server-side.
Features
Deployment
Single REST API call — no SDK, no library, any HTTP client works
Update artifacts in place — POST to /wp-json/wp/v2/artifacts/{id} and the public URL stays the same
Optional artifact_description field for internal documentation
Head content preservation — <meta> tags and other <head> elements from submitted HTML are preserved in output
External script support — <script src="..."> tags are registered as external dependencies and enqueued alongside local assets
Asset cache busting — enqueued files are versioned with filemtime() so browsers fetch updates automatically
Clean redeploys — old asset files are deleted before new ones are written
Security
Content Security Policy on every artifact page — blocks external script injection and cross-origin data exfiltration by default
Trusted CDN list out of the box: cdn.jsdelivr.net , unpkg.com , cdnjs.cloudflare.com , esm.sh , cdn.skypack.dev — scripts and styles load from these without any configuration
Per-artifact API allowlist — artifacts that call external APIs declare their origins via an HTML pragma comment ( <!-- artifact:fetch https://api.example.com --> ) or a deploy-time meta field; the plugin adds them to connect-src automatically
Custom capability type — artifact capabilities are separate from standard post capabilities; only Administrators can create artifacts by default
Developer Hooks
botcreds_agent_artifacts_csp — filter the full CSP header value for any artifact
botcreds_agent_artifacts_allowed_html — filter the wp_kses allowed-tags array
botcreds_agent_artifacts_grant_to_role() — helper to grant capabilities to additional roles
Custom template — drop single-artifact.php in your active theme to replace the render template
Use Cases
OpenClaw (AI personal assistant)
OpenClaw agents can deploy interactive dashboards, daily digests, data visualizations, and mini-apps in a single tool call. Generate the HTML, POST it, get the URL — no manual steps, no context switching.
For artifacts that fetch live data, add a pragma comment to the HTML and the CSP is updated automatically:
For recurring reports (daily digests, weekly summaries), store the artifact ID after the first deploy and update in place on subsequent runs. The URL never changes.
Claude Code (terminal-based coding agent)
Claude Code sessions can invoke a shell deploy script directly after generating output. Add a scripts/deploy-artifact.sh to your project and reference it in your CLAUDE.md — Claude will use it to ship outputs without leaving the terminal. No manual copy-paste, no browser switching.
Codex (OpenAI coding agent)
Same pattern as Claude Code. Add deployment instructions to your AGENTS.md and Codex can write HTML, call the deploy script, and report the live URL — all in one agent run.
GitHub Actions (versioned project)
For projects that build a static HTML output — dashboards, reports, documentation, changelogs — a GitHub Actions workflow can deploy to an artifact on every push to main . The artifact ID is stored as a repository variable so the public URL stays stable across all future deploys. Push → build → deploy → done.
Example: Deploy via REST API
curl -X POST "https://your-site.com/wp-json/wp/v2/artifacts" \ -u "username:application-password" \ -H "Content-Type: application/json" \ -d '{ "title": "My App", "status": "publish", "meta": { "artifact_html": "<!DOCTYPE html><html><body><h1>Hello.</h1></body></html>", "artifact_description": "Built by my AI agent" } }'
The response link field is the public URL of the deployed artifact.
Example: Artifact with Live Data
Include the fetch pragma in your HTML — no configuration needed:
01Upload the botcreds-agent-artifacts folder to /wp-content/plugins/
02Activate BotCreds Agent Artifacts in the WordPress admin under Plugins
03Go to Settings → Permalinks and click Save Changes to flush rewrite rules
04Create a WordPress Application Password for your agent user: Users → Profile → Application Passwords
03 / Source details
Frequently asked questions.
Does this work with any REST client or AI agent?
Yes. Any HTTP client that can POST JSON with Basic Auth (username + Application Password) works. No SDK or special library required. curl, Python’s urllib, Node’s fetch — anything goes.
Are artifacts sandboxed?
Artifact pages are served with a Content Security Policy that blocks external script injection and cross-origin fetch/XHR by default. The CSP is filterable ( botcreds_agent_artifacts_csp ) for custom use cases, and per-artifact API origins can be declared via the artifact:fetch pragma or the artifact_connect_src meta field.
What scripts and CDNs are allowed without configuration?
The following CDNs are in the default script-src allowlist: cdn.jsdelivr.net , unpkg.com , cdnjs.cloudflare.com , esm.sh , cdn.skypack.dev . External modules loaded from these CDNs work in artifact HTML without any additional configuration.
How do I allow my artifact to call an external API?
Two options:
Option 1 — HTML pragma (recommended): Add a comment to your submitted HTML:
The plugin strips the comment from output and adds the origin to connect-src .
Option 2 — Deploy-time meta field: Pass artifact_connect_src as an array: “meta”: { “artifact_connect_src”: [“https://api.example.com”] }
Both options accept only https:// origins. No wildcards, no http:// .
How do I update an artifact without changing its URL?
POST to /wp-json/wp/v2/artifacts/{id} with the same fields. The existing asset files are cleared, new files are written, and the public URL ( /artifacts/{slug}/ ) does not change.
What HTML elements and attributes are allowed?
The plugin allows a superset of wp_kses_allowed_html('post') including <canvas> , <svg> , <path> , <input> , <button> , <select> , <option> , <label> , <video> , and <audio> with their common attributes. data-* attributes are allowed on interactive elements. Additional tags and attributes can be added via the botcreds_agent_artifacts_allowed_html filter.
Who can create artifacts?
Only Administrators by default. To grant access to additional roles:
Yes. Place single-artifact.php in your active theme and it takes precedence over the plugin’s default template. The plugin template is used as a fallback.
Will my old artifacts still work after upgrading?
Yes. Artifacts created before v1.0 (stored as raw HTML) are still rendered via a legacy fallback path. No migration needed.
FinderPress Media Auditor helps site administrators scan for broken images, missing Media Library files, unreachable media URLs, and other media issues across WordPress content. Use it to audit images, video, audio, PDFs, featured images, and attachment files without sending scan data to an external
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati