Skip to main content

Vobiz agent and developer discoverability handoff

Audience: Frontend, web platform, documentation, developer relations, and platform engineering Prepared: July 21, 2026 Primary goal: Make Vobiz developer resources easy for search engines, AI agents, ChatGPT, Codex, Claude, and developer-directory scanners to find and verify.

Executive summary

Yes, we can support ChatGPT and Codex in addition to Claude. OpenAI now distributes apps and skills as plugins. A public plugin can contain skills, an MCP-backed app, or both. After review and publication, the same plugin appears in the Plugins Directory used by ChatGPT and Codex. We do not need two independent public submissions. The recommended Vobiz package is an app-plus-skills plugin:
  • Reuse the 13 public Vobiz agent skills.
  • Connect the public Vobiz documentation MCP server.
  • Expose a small, safe set of documentation tools.
  • Submit the package through the OpenAI plugin portal.
  • Add the approved directory URL to the Vobiz website and docs.
The scan shown in the issue is partly stale. The website now exposes several resources that the scan reported as missing. The team should still complete the remaining work and run a new scan before claiming a higher score.

Current score and progress

The supplied report shows a Discovery score of 7/20. The four visible scored rows account for 4/12 credited points: The report labels some additional checks as emerging or not scored. Track them because they improve agent discovery even when they do not immediately change the numeric score.

Workstream summary

Live verification completed on July 21, 2026

The following public URLs returned HTTP 200: The following discovery URLs returned 404:
  • https://vobiz.ai/.well-known/ai-catalog.json
  • https://vobiz.ai/server.json
  • https://vobiz.ai/mcp.json
The MCP server card is already the strongest of these discovery endpoints. The other three are optional or ecosystem-specific. Do not create undocumented JSON formats only to remove a 404. Add them only after confirming the current specification expected by the target registry or scanner.

What is already working on the main website

The rendered homepage contains crawlable links for:
  • API Reference
  • OpenAPI Specification
  • MCP Server
  • Developer Console
  • Agent Skills
  • API documentation
This is meaningful progress against the old 0/6 result. Keep these links as server-rendered <a> elements. Do not replace them with JavaScript-only click handlers. The docs domain also redirects correctly:
  • https://docs.vobiz.ai/introduction redirects to https://vobiz.ai/docs/introduction.
  • The final page identifies the vobiz.ai/docs URL as canonical.
Maintain this single canonical-domain strategy. Do not allow both domains to return independently indexable copies.

Frontend priority 0: create a developer discovery hub

Create or maintain a stable page at:
Use a server-rendered page. Give every resource a normal anchor link and a short text description. The page should be useful without JavaScript.

Required page content

Use these exact concepts in the title, heading, copy, and link labels:
  • Vobiz developer resources
  • Vobiz API documentation
  • Vobiz OpenAPI specification
  • Vobiz MCP server
  • Vobiz Agent Skills for Claude and Codex
  • Vobiz SDKs
  • Vobiz developer console
  • Vobiz Voice API
  • Vobiz SIP trunking API
  • Vobiz AI voice agent integrations
Suggested metadata:
Suggested resource list:
After OpenAI approves the plugin, add:
Do not publish a placeholder ChatGPT or Codex directory link. Add it only after the plugin is approved and published.
  • Add Developers to the main header or primary product navigation.
  • Keep API Reference, OpenAPI Specification, MCP Server, Developer Console, and Agent Skills in the global footer.
  • Add a link from the docs introduction back to /developers.
  • Add links between the MCP, skills, OpenAPI, and SDK pages.
  • Add the OpenAI directory link to both the main-site footer and the docs tools section after publication.

Technical SEO requirements

  • Return 200 without requiring authentication.
  • Render the title, description, heading, body copy, and links on the server.
  • Include /developers in https://vobiz.ai/sitemap.xml.
  • Keep robots.txt permissive for standard search and AI crawlers.
  • Use one canonical URL per resource.
  • Avoid fragment-only navigation for critical resources.
  • Avoid links hidden behind consent, login, hover, or client-side state.
  • Return application/json for JSON resources and text/plain for llms.txt, agents.md, and robots.txt where practical.
  • Preserve stable URLs. Directory submissions and agents may cache them.

Structured data

Add Organization and WebSite JSON-LD to the main website. Connect the public developer properties using sameAs and subjectOf where appropriate. Do not claim third-party verification or an official directory listing before approval. At minimum, the organization object should consistently identify:
  • Name: Vobiz
  • URL: https://vobiz.ai
  • Logo: a stable absolute HTTPS URL
  • GitHub: https://github.com/vobiz-ai
  • LinkedIn: the official Vobiz company URL
  • X: the official Vobiz account URL
  • Support or contact URL
Validate structured data in a schema validator before deployment.

ChatGPT and Codex implementation plan

Publish one OpenAI plugin named Vobiz Developer or Vobiz with:
  • The 13 existing Vobiz skills.
  • A documentation app backed by the public MCP server.
  • Starter prompts for API integration, Voice XML, SIP trunks, phone numbers, audio streams, and AI voice agents.
  • Public Vobiz privacy, terms, support, website, and documentation URLs.
Use an app-plus-skills submission. It gives ChatGPT a live documentation source and gives Codex reusable implementation workflows.

Important MCP review issue

The current server card describes the server as read-only, but it advertises a submit_feedback tool. That tool changes state by creating a feedback report. Before OpenAI submission, choose one of these approaches:
  1. Recommended: expose only read-only documentation tools to the public OpenAI app.
  2. Keep submit_feedback, but describe and annotate it as a write tool.
For the cleanest first review, expose a narrow tool set:
  • search_vobiz_docs
  • fetch_vobiz_doc
  • get_vobiz_api_operation
Avoid presenting a general shell-like documentation filesystem tool to reviewers. The current query_docs_filesystem_vobiz description mentions commands such as grep, find, cat, and jq. Even if it is sandboxed, a narrowly scoped fetch tool is easier for users and reviewers to understand. Recommended annotations for the three documentation tools: If submit_feedback remains available: Confirm these values against the actual implementation before submission.

OpenAI submission prerequisites

  • Use the OpenAI organization that represents Vobiz.
  • Complete business verification for the Vobiz publisher name.
  • Give the submitter Apps Management: Write permission.
  • Use a project with supported global data residency.
  • Host the MCP server at a public production URL.
  • Keep the MCP origin stable. Changing the origin later requires a new app submission.
  • Define the required content security policy for every external domain the app uses.
  • Host the exact domain verification token at /.well-known/openai-apps-challenge when the portal supplies it.
  • Ensure the privacy policy discloses every category of user-related data returned or processed.
  • Remove auth tokens, debug payloads, internal identifiers, and unnecessary personal data from tool results.

OpenAI submission materials

Prepare:
  • Plugin name
  • Short description
  • Long description
  • Square logo and production brand assets
  • Category
  • Website URL
  • Support URL
  • Privacy policy URL
  • Terms URL
  • Production MCP URL
  • Accurate tool metadata and schemas
  • Starter prompts
  • Exactly five positive review test cases
  • Exactly three negative review test cases
  • Country availability
  • Initial release notes
Submission portal:
After approval, the publisher must click Publish. Approval alone does not make the listing searchable.

Suggested listing copy

Plugin name
Short description
Long description

Suggested starter prompts

  • “Show me how to place an outbound call with the Vobiz API in Node.js.”
  • “Build a Vobiz Voice XML IVR that collects one digit and routes the caller.”
  • “Explain how to connect a Vapi agent to a Vobiz SIP trunk.”
  • “Find the Vobiz API operation for purchasing and assigning a phone number.”
  • “Create a bidirectional WebSocket audio-streaming example for an AI voice agent.”
  • “Review this Plivo integration and show the changes needed to migrate it to Vobiz.”

Review test plan

Positive cases must have deterministic expected behavior. Recommended cases:
  1. Find and explain the make-call API operation without inventing fields.
  2. Generate valid Vobiz Voice XML for a simple IVR.
  3. Explain Vobiz SIP trunk authentication and registration.
  4. Find the correct phone-number purchase or assignment workflow.
  5. Explain the bidirectional Stream event sequence and supported audio format.
Recommended negative cases:
  1. Refuse to reveal or infer another customer’s Vobiz credentials.
  2. Do not claim that a documentation-only tool placed a real phone call.
  3. Do not submit feedback, purchase a number, or release a number without a tool that explicitly supports that action and the required user confirmation.
Test every case in ChatGPT web and mobile before submission.

Codex repository packaging

The public repository already includes:
  • skills/ with 13 Vobiz skills
  • .mcp.json
  • .claude-plugin/plugin.json
  • .claude-plugin/marketplace.json
The following public files are currently missing:
  • .codex-plugin/plugin.json
  • .agents/plugins/marketplace.json
Add them to https://github.com/vobiz-ai/Agent-Skills. Recommended repository shape:
Draft Codex manifest:
Validate the manifest against the current Codex plugin tooling before merging. If the final plugin exposes the feedback write tool, change the public capability description so it does not imply a strictly read-only package. After the repository marketplace is merged, test:
Open the Codex plugin browser, install Vobiz, restart the session, and verify that all 13 skills and the MCP connection load.

Public agent platform configuration files

The scanner reported no public agent configuration. Its probes looked for .claude/, .cursor/, and .windsurf/ content. The public Agent-Skills repository currently does not contain these checked files:
  • AGENTS.md
  • .cursorrules
  • .cursor/rules/vobiz.mdc
  • .windsurf/rules/vobiz.md
  • .github/copilot-instructions.md
Add concise configuration files to the public repository. Each file should:
  • Explain that Vobiz is a programmable telephony platform.
  • Link to the canonical docs, OpenAPI, MCP server, and skills index.
  • Direct the agent to the appropriate skills/vobiz-* directory.
  • State the correct authentication conventions without including credentials.
  • Warn against inventing API fields or endpoints.
  • Require confirmation before actions that spend money, send communications, purchase numbers, place calls, or release resources.
  • Avoid duplicating all 13 skills into every platform file.
The AGENTS.md in this Mintlify repository is still a generic template. Customize it with Vobiz terminology, repository validation commands, content boundaries, and a credential-safety rule. The public Agent-Skills repository also needs its own tailored AGENTS.md.

Skills.sh follow-up

The direct Vobiz page is live:
The remaining issue is keyword search and “Official” curation.
  • Keep the public repository name, organization, README, and skill metadata consistent.
  • Link the skills.sh page from /developers and the docs skills page.
  • Report the missing vobiz search result to skills.sh/Vercel with the direct listing URL.
  • Treat “Official” as third-party curation. Do not add an official badge to Vobiz pages unless skills.sh grants it.
  • Recheck exact-name search after the site reindexes the repository.

MCP registry work

The Vobiz MCP server card is live, but the report did not find Vobiz in MCP registries. Platform or DevRel should submit the public MCP server to relevant registries using:
  • Name: Vobiz Docs
  • Publisher: Vobiz
  • Endpoint: https://vobiz.ai/docs/mcp
  • Server card: https://vobiz.ai/.well-known/mcp/server-card.json
  • Documentation: https://vobiz.ai/docs/resources/mcp
  • Authentication: public/no authentication for documentation lookup
  • Repository or support link: the official Vobiz GitHub organization or support page
Do not describe the full server as read-only while submit_feedback remains available. Either remove that tool from the public registry surface or describe it accurately.

Frontend acceptance criteria

The frontend portion is complete when all checks below pass:
  • /developers returns 200 and appears in the main sitemap.
  • The page has one unique title, description, canonical URL, and h1 in the production prerender.
  • Critical resource links are present in server-rendered HTML.
  • The global header and footer link to /developers on desktop and mobile.
  • The footer preserves links to API docs, OpenAPI, MCP, console, Agent Skills, skills.sh, and the MCP server card.
  • robots.txt allows search and approved AI crawlers.
  • JSON and plain-text resources return appropriate content types.
  • docs.vobiz.ai redirects to the canonical vobiz.ai/docs route.
  • No private repository, staging host, local URL, or secret appears in public markup.
  • No placeholder OpenAI directory URL is published before approval.
  • The OpenAI directory link is crawlable from both the homepage and /developers.
  • Organization structured data validates successfully.
  • Mobile and desktop layouts expose the same developer links.

Frontend implementation status

  • Added the /developers route and responsive developer hub.
  • Added /developers to build-time metadata injection and the 39-route prerender pipeline.
  • Added /developers and /server.json to the main sitemap.
  • Added crawlable developer links to the global navigation and footer.
  • Added CollectionPage and ItemList structured data for the developer hub.
  • Added GitHub, LinkedIn, X, support, developer hub, OpenAPI, and MCP relationships to Organization structured data.
  • Added and validated the official MCP Registry server.json manifest.
  • Corrected the MCP server card to protocol 2025-06-18 and documented submit_feedback as a write operation.
  • Added the canonical Vobiz Docs MCP endpoint and installation command to /developers.
  • Synchronized the Vobiz Docs identity, version, website, icon, transport, endpoint, tools, and authentication details across the Registry manifest, server card, developer hub, and MCP guide.
  • Expanded the Agent Skills discovery index from 2 task skills to 15 digest-pinned Vobiz skills and added automatic SHA-256 generation.
  • Added the developer-hub backlink and MCP discovery metadata to the Mintlify documentation.
  • Production build succeeded and all 39 routes prerendered.
  • Targeted lint, unit tests, JSON validation, XML validation, and desktop/mobile visual checks passed.
  • Merge and deploy feat/developer-discovery-hub from devlume-in/vobiz-website.
  • Deploy the Mintlify introduction and MCP page updates.
  • Verify the modified public URLs after deployment.

Repository and platform acceptance criteria

  • .codex-plugin/plugin.json exists on the public repository’s default branch. It is implemented on feat/public-agent-configs; merge pending.
  • .agents/plugins/marketplace.json exists on the public repository’s default branch. It is implemented on feat/public-agent-configs; merge pending.
  • Codex installs the flat-root marketplace and plugin in an isolated CODEX_HOME test and discovers all 13 skills.
  • Public agent configuration files exist and link to canonical Vobiz resources.
  • The MCP app surface exposes narrow, accurately annotated tools.
  • Vobiz business identity is verified in the OpenAI organization.
  • The submitter has Apps Management write access.
  • Five positive and three negative test cases pass.
  • The OpenAI plugin is submitted, approved, and explicitly published.
  • The final directory URL is added to the Vobiz website.
  • Vobiz is submitted to selected MCP registries.
  • skills.sh exact-name search is rechecked or escalated.

Agent-Skills repository implementation status

  • Added .codex-plugin/plugin.json with skills, MCP, legal URLs, branding, capabilities, and starter prompts.
  • Added .agents/plugins/marketplace.json using the CLI-tested flat repository source path ..
  • Preserved and validated .claude-plugin/plugin.json and .claude-plugin/marketplace.json.
  • Added official Vobiz PNG icon and logo assets.
  • Pointed .mcp.json to the canonical https://vobiz.ai/docs/mcp endpoint.
  • Corrected the MIT license copyright to Ilaimitado Private Limited.
  • Added Codex install, verification, and usage instructions to the README.
  • Added CI checks for manifests, 13-skill count, PNG signatures, MCP paths, and flat marketplace source.
  • Codex validator, isolated marketplace installation, Claude strict validation, Skills CLI discovery, and linked URL checks passed.
  • Merge feat/public-agent-configs into the public repository’s default branch.

Search Console indexing checklist

Run this after the website and docs deployments. Treat it as a regular release practice whenever a developer-discovery URL is added or materially changed.

Submit the modified URLs

  • Inspect and request indexing for https://www.vobiz.ai/developers.
  • Inspect and request indexing for https://vobiz.ai/docs/introduction.
  • Inspect and request indexing for https://vobiz.ai/docs/resources/mcp.
  • Inspect and request indexing for https://vobiz.ai/docs/resources/skills.
  • Inspect and request indexing for https://vobiz.ai/openapi.json.
  • Inspect and request indexing for https://vobiz.ai/.well-known/mcp/server-card.json.
  • Inspect and request indexing for https://vobiz.ai/server.json.
  • Inspect and request indexing for https://vobiz.ai/agents.md.
  • Inspect and request indexing for https://vobiz.ai/llms.txt.
  • Resubmit https://www.vobiz.ai/sitemap.xml in Google Search Console.
  • Confirm each HTML URL is canonicalized to the intended host and each machine-readable URL is fetchable.
  • Record the submission date, indexing result, and owner in the release ticket.

Recurring release practice

  • Add changed public developer URLs to the release checklist before deployment.
  • Request indexing after the production deployment, not from a preview URL.
  • Recheck indexing after 3-7 days and investigate excluded or duplicate URLs.
  • Run the external developer-discoverability scan again after indexing settles.
  • Compare the new score against the 7/20 baseline and attach the result to the release ticket.

Suggested one-week execution order

Day 1: frontend discovery

  • Create /developers.
  • Verify server-rendered links and metadata.
  • Add the route to header/footer and sitemap.
  • Deploy and validate canonical behavior.

Day 2: Codex packaging

  • Add the Codex manifest and marketplace.
  • Add icon and logo assets.
  • Test repository installation in Codex.
  • Add public agent configuration files.

Day 3: MCP app hardening

  • Replace the shell-like docs query with narrow search/fetch tools for the OpenAI surface.
  • Hide or correctly annotate submit_feedback.
  • Add output schemas, annotations, and CSP.
  • Test the production MCP endpoint externally.

Day 4: OpenAI submission preparation

  • Complete Vobiz business verification.
  • Confirm submitter permissions.
  • Prepare listing copy, assets, legal URLs, prompts, and test cases.
  • Complete the domain challenge and scan tools.

Day 5: submit and rescan

  • Submit the OpenAI plugin for review.
  • Submit the MCP server to relevant registries.
  • Report the skills.sh search issue if it remains unresolved.
  • Run the developer-discoverability scanner again.
  • Save the new report and compare each row with this baseline.
OpenAI review time is external and cannot be guaranteed within the week. The team can complete the technical submission during the week, but the ChatGPT app listed score changes only after OpenAI approves and the publisher clicks Publish.

Final definition of done

Do not close this workstream merely because the files exist in a repository. Close it when:
  1. Public URLs return the expected content.
  2. The main website links to them in crawlable HTML.
  3. Codex can install and use the plugin.
  4. OpenAI has approved and published the plugin for ChatGPT and Codex.
  5. The published directory URL appears on the Vobiz website.
  6. A fresh external scan recognizes the resources.

References