frontman.sh valid
Frontman
Ship updates to your existing WordPress site faster with Frontman's AI editor. Describe one update, inspect the page, and refine the result. Next.js, Astro, and Vite use a separate development and source-review workflow.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://frontman.sh/llms.txt
- llms-full.txt
- https://frontman.sh/llms-full.txt
- Sections
- 9
- Links
- 42
- Size
- 8441 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T08:20:34.616Z
- Last checked
- 2026-10-25T08:20:35.537Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T08:20:34.620Z. Cached copy · Source on frontman.sh
# Frontman
> Ship updates to your existing WordPress site faster with Frontman's AI editor. Describe one update, inspect the page, and refine the result. Next.js, Astro, and Vite use a separate development and source-review workflow.
## WordPress
Install [Frontman from the WordPress Plugin Directory](https://wordpress.org/plugins/frontman-agentic-ai-editor/), activate it, and open Frontman from the WordPress admin menu. Requires WordPress 6.0+, PHP 7.4+, administrator access, Frontman sign-in, service access, and your own supported AI provider with separate costs. Frontman for WordPress is production-ready. Start with staging and backups. WordPress-native writes persist to the connected installation; published content on a live site can change immediately. Preview is not a universal approval gate.
- [WordPress homepage](https://frontman.sh/)
- [WordPress setup guide](https://frontman.sh/docs/integrations/wordpress/)
- [Framework workflow and installation](https://frontman.sh/frameworks/)
The following sections describe the framework workflow.
## What problem does Frontman solve?
Known website updates still need implementation: builder controls, file hunting, or handoffs. Frontman brings the request and rendered page into one editing loop. Inspect the result and refine it; visual context does not guarantee correctness.
## Who is Frontman for?
- **Designers** who want to make spacing, typography, color, and layout changes directly in the running app without opening an IDE or filing a ticket. Source changes still need developer review, tests, and deployment.
- **Product managers** who need to update copy, tweak structure, or explore feature ideas without waiting for an engineering sprint. Frontman gives non-technical teammates a chat interface alongside a live view of the app.
- **Frontend developers** who want faster iteration with richer context than terminal-based AI tools provide. Click an element, describe the change, see it happen — instead of writing prompts that specify file paths and line numbers.
- **Teams** that want to collapse the gap between "people who can describe a change" and "people who can make a change" — while keeping the entire engineering review process intact.
## How it works
Framework integrations require a running supported development project and permitted workspace access. They expose source and dev-server context alongside browser tools for DOM, styles, and selection. A hosted or self-hosted Frontman server orchestrates tasks and sends relevant context to the selected AI provider. WordPress uses native CMS tools, not the framework filesystem tools.
Frontman is intended for development workflows. RuntimeEnv disables the integration outside development by default, with explicit enable overrides. This is a runtime guard, not automatic build stripping. Check the configuration, built artifact, and deployed `/frontman` route when Frontman must be absent. Source changes use your team's normal Git review, tests, and
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| postman.ai | Postman AI | interface Cybersecurity AI agents and MCP +2 | — | 46 | ✓ | ||
| wordpress.com | WordPress.com | interface APIs and SDKs | US | 75 | ✓ | ||
| frontstream.com | FrontStream Docs | documentation Finance and payments Documentation and reference | — | 60 | ✓ | ✓ | |
| mainwp.com | MainWP | interface Business software Open source projects | US | 59 | ✓ | ||
| fumadocs.dev | Docs | documentation Developer tools Documentation and reference | US | 45 | ✓ | ✓ | |
| readme.com | ReadMe | documentation AI and machine learning Developer tools +1 | US | 60 | ✓ | ||
| postman.com | Postman | interface AI agents and MCP Developer tools +1 | US | 70 | ✓ | ✓ | |
| gptw.com.br | GPTW | interface | BR | 60 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=frontman.sh · GET /v1/domain/frontman.sh · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage frontman.sh, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for frontman.sh:
1. POST https://agentwebmap.com/v1/sites/frontman.sh/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://frontman.sh/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/frontman.sh/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/frontman.sh).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.