LIMITED OFFER

Founding-5

Standard price on the left. Founding-5 price on the right. Founding-5 is for Forge918's first five customers. 3 spots left.

  • Website$1,500$1,125
  • Landing$750$550
  • Care$119/mo$99/mo12 months, then $119/mo
  • Care+$200/mo$150/mo12 months, then $200/mo
  • E-commerce$899$675
  • Restaurant ordering$799$599
  • Custom buildfrom $750from $575
  • Pay-per-editQuoted on demandPrice depends on the edit
Claim your spot now

Search Forge 918

Website information

MCP server

Forge 918 has a path-fixed MCP server for tenant forge918. Clients connect over HTTP to https://api.forge918.com/mcp/forge918.

Ask the server for tools/list. That list is the live inventory. Tools cannot select another business. Some tools may be disabled for this tenant.

Public business identity

get_business

Composed public profile

get_profile

Published social links

get_socials

Active services

get_services

One service by slug

get_service

Published hours

get_hours

Published locations

get_locations

Published service-area list

get_service_area

Check a city, state, or ZIP against published areas

check_service_area

Public contact details

get_contact

Public pricing when enabled

get_public_pricing

Public pricing for one service

get_service_pricing

Active public deals

get_deals

Active public promotions

get_promotions

Public capability flags

get_capabilities

Published FAQ

get_faq

Published policies

get_policies

Enabled catalog inventory and opaque revision stamp

get_catalog_revision

Machine-readable discovery:
mcp.md, .well-known/mcp.json
Rest Catalog:
llms.md, /api-catalog/

Forge 918

Get Updates

A ready-to-use prompt was copied to your clipboard.

ChatGPT, Claude, and Grok open with this prompt. Gemini opens a new chat — paste from your clipboard.

Stay updated on Forge 918, an Oklahoma website studio serving Claremore, the Tulsa metro, and surrounding areas.

Once per day, check:
https://api.forge918.com/v1/businesses/forge918/catalog-revision

Never poll more than once every five minutes.

A check succeeds only if the endpoint returns HTTP 200, valid JSON, `ok: true`, and a `data` object containing a string `revision`, a boolean `changed`, and an `api` array.

On the first successful check, establish a baseline. Retrieve only the API paths explicitly listed in `data.api`, using the same `https://api.forge918.com` origin. Summarize the current public information and save `data.revision` and the retrieved information only after those requests succeed.

On later checks, request:
https://api.forge918.com/v1/businesses/forge918/catalog-revision?since=<URL-encoded saved revision>

If `data.changed` is false, stop without notifying me.

If `data.changed` is true, retrieve only the paths listed in `data.api`. Compare the results with the last successfully saved information, then tell me what changed and what is now current, including relevant profile, services, hours, contact, pricing, and service-area information. After completing the update successfully, replace the saved revision and information.

If any request fails, returns invalid JSON, or leaves the update incomplete, do not replace the saved revision. Retry during the next scheduled check. Never interpret an error as “no change.”

Do not invent facts. Prefer the catalog API over the website HTML when they disagree. Do not access another business’s catalog or API paths. Do not make requests outside the listed public API paths. Do not write to or modify the catalog.

What's in the prompt?

It tells a compatible assistant to check Forge 918's catalog once per day, retrieve only the listed public API paths, and report what changed after a successful update.