Overview
Your business profile is the source of truth for your Ready MCP server. When you update your profile, your MCP server automatically redeploys with the new configuration.ezForge Ready is currently in development. This page describes the planned business profile management experience.
Redeploys are batched
If you make several edits in quick succession (for example, updating your hours and then your description a moment later), Ready combines them into a single redeploy rather than triggering one per edit. If an edit arrives while a redeploy triggered by an earlier edit is still in progress, it isn’t lost — Ready automatically follows up with another redeploy once the in-progress one finishes, so your latest saved changes are included in the follow-up redeploy.Recovering from a failed redeploy
If a redeploy fails to reach your MCP server (for example, a temporary infrastructure issue), your server keeps serving its last successfully deployed configuration rather than a broken one. When this happens, a banner appears across your dashboard linking to/ready/dashboard/republish, which shows a Configuration failed to deploy notice with a Republish button — click it to retry sending your current configuration. Otherwise it says there’s nothing to republish. Republish always resends your saved configuration, even if it looks identical to what’s already deployed, so it recovers a server stuck on last-known-good after a failed deploy (except IMAGE_TOO_OLD_FOR_CONFIG, which needs a server image update first — see Redeploy safeguards).
Redeploy audit trail
Every redeploy that actually writes a new configuration (an automatic redeploy of an identical configuration is skipped; Republish is always recorded) is recorded in an internal, append-only audit trail with the reason it was triggered (for example, onboarding or a profile edit) and the user who triggered it. If the redeploy then fails to reach your MCP server, a second entry records the failure and its error message (truncated to 2,000 characters). The audit trail is not exposed through the public API or the dashboard; it is used to power the failed-redeploy recovery flow above and for troubleshooting.Redeploy safeguards
Every redeploy runs through a single path that assembles your configuration from your profile, validates it, and only then saves and deploys it. The first five checks below run before anything is written, so a rejected redeploy never changes what your MCP server is serving. The image check and the rollback after it apply at the deploy step:- Validation. A configuration that fails schema validation is rejected (error code
INVALID_CONFIG, HTTP 422) and nothing is saved or deployed. - Size limit. The serialized configuration must be at most 4,194,304 bytes (4 MiB) uncompressed, and its compressed delivery payload (the request that updates your server) at most 524,288 bytes (512 KB). A configuration over either limit is rejected (error code
CONFIG_TOO_LARGE, HTTP 422) rather than truncated — reduce the amount of catalog or business data and try again. - Unchanged configuration. If the newly assembled configuration is identical to the one already saved, the redeploy is skipped: nothing is written and your server is not touched. Republish bypasses this check and always redeploys.
- Provisioned server required. The business must already have a server with a machine assigned to receive the configuration. If the server has no machine yet, the redeploy fails with
NO_MACHINE(HTTP 409); if the business has no server at all, it fails with a not-found error. - Industry type. Your template type (restaurant, salon, and so on) is preserved from the one your business was already assigned. The first redeploy for a business must be given it explicitly (the setup wizard does this); if it can’t be determined, the redeploy fails with
TEMPLATE_TYPE_UNKNOWN(HTTP 422) instead of defaulting to another vertical. It also fails this way if your business’s assigned industry type isn’t yet supported by Ready configurations. - Server image must support the configuration. Before updating your server, Ready checks which template image it is running. Current Ready configurations (version 3.0), and any configuration over 32,768 bytes serialized, are only sent to a server whose image is known to load them; an older image would fail to start with the new configuration and crash-loop. If the image isn’t known to be capable — including when its image digest can’t be determined — the redeploy is refused with error code
IMAGE_TOO_OLD_FOR_CONFIG(HTTP 409) and the configuration is not sent. The check only reads the image and never changes it, so your server keeps running its last successfully deployed configuration. It runs as part of the deploy step, so it is handled like any other failed deploy (see “Failed deploys are rolled back” below), and Republish fails the same way until the server’s image is updated to a current template image — an ezForge operations step, not something you can do from the dashboard. - Failed deploys are rolled back. If the configuration is saved but the deploy to your MCP server then fails, the saved configuration is reverted to its previous value on a best-effort basis, so an identical retry isn’t mistaken for an already-deployed configuration and skipped.
Profile sections
Business information
Core details that identify your business to AI agents:- Business name — How agents refer to your business
- Address — Physical location (used for location-based discovery)
- Phone number — Contact number (also used for verification)
- Website — Link to your existing website (if any)
- Description — Short description agents use to understand your business
Hours of operation
- Regular weekly hours
- Holiday schedules and special hours
- Temporary closures
Services & offerings
Your catalog is managed through a universal item editor in the dashboard. Items share common fields (name, description, price, category, availability, and optional “Also known as” aliases that agents use when searching) and vertical-specific metadata:- Restaurants: Menu items, dietary tags, calories, spice level
- Salons: Service list, duration, stylist assignments, walk-in availability
- Home Services: Service catalog, service area, pricing type (fixed/hourly/estimate), contractor credentials (license numbers, types, insurance provider, expiration dates)
- Retail: Products, SKUs, inventory status, shipping availability
- Professional Services: Consultations, credentials, insurance acceptance, specializations
Agent capabilities
Control what AI agents can do:
All booking and ordering requests are forwarded to you via email and SMS for confirmation — no automated transactions without your approval.
Subdomain
Every Ready business gets a permanent subdomain:Verification badge
Your Ready settings page (/ready/settings) displays a verification badge showing your current trust tier. The badge is color-coded by level:
Below the badge, the settings page shows a description of what the current tier means and a Next step prompt explaining how to advance — except at Premium Verified, where no further steps apply.
Advancing through tiers
- Unverified → Phone Verified — Click Verify phone on your settings page. Ready sends an SMS code to your registered business phone number. Enter the code to complete verification immediately.
- Phone Verified → Business Verified — No action required. The system runs an automatic eligibility check after your account is at least 30 days old and phone-verified. When both criteria are met, your tier upgrades automatically (Google Business Profile cross-reference is in Beta — logs but is not blocking).
- Business Verified → Premium Verified — Click Apply for Premium on your settings page to enter the manual review queue. The ezForge team reviews your business and promotes the tier after approval.