8:45 PMLabs

Labs / Archive note · Updated 2026-10-06

We read OpenAI's plugin rules before building one. One idea died on the first page.

We read OpenAI's plugin rules before building one. The directory is real, and so is the review. One idea ended on the first page.

PlannedDecided, not built.
  1. Read the rules
  2. Check each candidate
  3. Drop the prohibited one
  4. Apply as a provider
  5. Build in developer mode
  6. Submit
  7. Publish the review result

Explore with AI

Field report

01REVIEWED

What OpenAI asks for before it lists anything

A plugin is a package: a remote server that speaks MCP, optional written skills, and listing metadata. You upload it, OpenAI's automated checks scan the package and the server's tools, and then its review team tests it. After approval you choose when to publish.

The review wants specifics. Five test cases that should work, with the prompt, the tools expected to fire and the expected result. Three that should be refused. A recorded walkthrough. If the plugin needs a sign-in, a test account that works without a code sent to a phone or an inbox. The publisher has to be a verified person or business, and the server's domain has to be proven with a token at a well-known URL.

One detail matters for anyone maintaining these. After the first publication OpenAI rescans the server daily, and tool changes that pass the automated checks go live with no new submission. Changes to the listing or the skills need a new package.

The build is the short part. The submission is where the time goes, and OpenAI promises no date.

02REVIEWED

The rule that ended our first idea

The first plugin we sketched was for a credit-dispute product: look up the right dispute basis, draft the letter, track the response clock. It fit the mechanics well, because it needs an account and data ChatGPT doesn't have.

The guidelines list what plugins may not sell, promote or facilitate. Credit repair is on it, next to debt relief and credit-score manipulation schemes. We stopped there. A consumer-rights framing might survive a review and might not, and a plugin that can be removed after approval is a poor foundation.

Two other rules shape local work. Plugins may conduct commerce only for physical goods, so no service is sold in the chat. And a tool may not ask for a street address or precise location, which a tree quote needs. The address has to be collected in the plugin's own form or on the follow-up call.

Read the prohibited list before the quickstart.

03REVIEWED

The Get Quote button, and who it's for

This is the part that changes the picture for a local business. When someone searches for an eligible business in ChatGPT, the business card can show a Get Quote button. Selecting it opens the provider's quote form in the chat.

The contract is small. The provider exposes one tool, named request_service, and supplies a paginated feed of business records: an id, name, address, coordinates, phone, website, and a service-provider entry saying this business accepts quote requests. ChatGPT shows the button only when the business has an eligible provider with a configured partner plugin.

It is in beta with approved partners, and you apply through OpenAI's merchants form. We have not applied yet. That is the next step, and we may not get in.

A local business doesn't need its own plugin. It needs to be a correct record in a provider's feed.

04

What we're building first

Lehvel's general connection for AI assistants exists now. The next step is packaging those capabilities as Lehvel's own plugin and putting that package through OpenAI's current review flow. Then a provider plugin can expose approved business facts and actions for clients once each owner agrees.

We'll publish what the review says. If it's a rejection, the rejection is the entry.

What we asked and what we found

Every entry answers the same eight questions, in this order.

Question

Can a local business be something a customer acts on inside ChatGPT, and what would Lehvel have to build to put one there?

Why it matters

A post told founders to stop what they were doing and build a ChatGPT plugin. We read the submission guide, the plugin guidelines and the local-services quote specification first, and checked three candidate plugins against them.

State

Planned Decided, not built.

What we built or tested

  • A general connection that lets AI assistants call Lehvel's tools, with its own controls. That is groundwork. It is not a submitted or approved ChatGPT plugin.
  • A written check of three candidate plugins against OpenAI's published rules, dated 2026-10-02.

Evidence

Submission requirements (OpenAI, re-read 2026-10-06)
Verified publishing identity · MCP domain verification where used · five positive and three negative test cases for initial MCP review · video walkthrough · release notes
Plugin architecture (OpenAI, read 2026-10-06)
A plugin can package skills, an MCP server or both, with optional UI; ChatGPT and Codex share a universal plugin directory on supported surfaces.
Commerce rule, quoted
“Currently, plugins may conduct commerce only for physical goods.”
Prohibited services, quoted
“Debt relief, credit repair, or credit-score manipulation schemes”
Local-services Get Quote, quoted
“currently in beta and being tested with approved partners”
Review timeline
None published by OpenAI

What we learned

  • The category rule comes before the idea. Our first candidate was in a category OpenAI prohibits by name. Finding that took ten minutes and saved a build.
  • For a local business the plugin is not the prize. Nobody installs a tree service's plugin on purpose. What matters is a Get Quote button on the business's card in ChatGPT, and that is gated.
  • A plugin should not become a second copy of the business. The checked record and the controls stay separate.
  • A plugin cannot sell a service inside the chat. For local work the conversion was always a quote request.

Limitations

  • We have not packaged, submitted or received approval for a public ChatGPT plugin.
  • We have not applied to the Get Quote beta and do not know its acceptance criteria.
  • The rules were read on 2026-10-02. OpenAI reworked this system in July and again in September, and will again.

What changes next

Package Lehvel's existing connection as a first ChatGPT plugin, test it against the current review cases, complete publisher and domain verification, and submit. In parallel, apply to the local-services partner program.
Failed tests are published as results. A state on this page describes today, not plans.

Sources and credits

These tools belong to the people who made them. Lehvel reviewed and, where noted, tested them. Nothing here is a Lehvel product, and no performance figure attributed to a vendor has been reproduced by us.

Next in Labs

Explore with AI

Get Upstream

One note a week: one job we took off an owner's plate, and what came of it.

My posts reach 17,000+ followers across our channels. The weekly email is called Upstream.

Weekly. Unsubscribe anytime. Privacy

8:45 PMAll of Labs