Smithery Distribution
External listing only. The local MCP package and hosted MCP endpoint are built; marketplace acceptance remains outside the repo.
Roadmap
Roadmap
What comes next.
This page now tracks only what remains to build. Shipped product surfaces live in the changelog, docs, schema universe, benchmark page, and API reference.
Agent Distribution
Make agent interfaces easier to find and install.
Roadmap work now focuses on external registries and hosted access for environments that cannot run local packages.
MCP Directories
Submit to curated directories so developers can find the insurance extraction server by category and use case.
Accepted links
Add verified Smithery, MCP.Directory, mcp.so, and PulseMCP links only after those external listings are accepted.
Package registries
Keep npm package metadata, MCP server metadata, OpenAPI, llms.txt, and the agent manifest synchronized with shipped capabilities.
Milestones
Upcoming work only.
01
ActiveExternal dependency
External Approvals and Listings
- Submit connector packages and templates to platform review where marketplace approval is required.
- Keep marketplace, SOC, and certification language unclaimed until third-party acceptance exists.
- Add accepted external listing links back to agent, docs, connectors, and discovery pages only after approval.
02
NextCredentials required
Production Scale Activation
- Configure AWS/S3-compatible storage, queue abstraction, Bedrock provider, IAM/secrets, and observability credentials when the funded scale path is approved.
- Run load tests and operational drills before raising large package limits.
- Keep Cloudflare as the current live production path until the scale path is configured and verified.
03
UpcomingExternal dependency
Formal Security Audit
- Use Vanta or an equivalent compliance workflow once funded.
- Collect audit evidence for access controls, retention, deletion, incident response, vendor management, and change management.
- Do not claim SOC 1 or SOC 2 until an auditor issues the report.
Developer Universe
More ways to build on PolDex.
The next work is making integration faster, safer, and more versioned across developer environments.
Reference applications
Build account-specific reference examples only after real customer environments reveal which workflow runners matter most.
Versioned contracts
Keep API and schema versioning stable as FastScript upgrades deepen the 99%+ benchmarked surface.
Webhook receivers
Add more language-specific webhook receiver examples after customer integration demand is known.
Artifact workflows
Keep JSON, CSV, XLSX, signed-link, connector-event, and batch download examples synchronized with production routes.
Enterprise Universe
Controls for larger buyers.
Enterprise work should strengthen governance around the same API and ledger, not create a separate product that competes with customer workflows.
SOC 2 readiness
Move from preparation language into stronger controls, evidence collection, policy maturity, and audit readiness.
SSO provider setup
Wire customer-selected identity provider credentials after enterprise procurement requires a concrete provider.
Procurement packet review
Keep security, DPA, deletion, retention, audit, and subprocessor materials current for enterprise diligence.
Audit evidence
Move implemented controls into auditor-reviewed evidence when the audit engagement starts.
Distribution Universe
Make PolDex discoverable wherever builders look.
Search, agent directories, marketplaces, package registries, and proof-led docs all point back to the same extraction primitive.
Search
Keep Google, Bing, sitemaps, structured data, OpenAPI, llms.txt, llms-full.txt, and agent discovery files current.
Marketplaces
Submit and maintain external marketplace and directory listings after each platform review process accepts PolDex.
Public proof
Keep proof, benchmark, FastScript, docs, and changelog current as the proof-led distribution surface.
Technical docs as marketing
Publish examples that developers and agents can copy directly instead of relying on broad marketing pages.
Operating Principles
Non-negotiables.
01Roadmap only shows what is coming, not what already shipped.
02API remains the core product surface; processor and agent interfaces sit on top of the same rails.
03No hidden state transitions. Ledger and job state must reconcile.
04The 99%+ accuracy claim stays backed by public proof, benchmark publication, and release-gate evidence.
05New product lines reuse PolDex core primitives instead of spawning separate stacks.
See what already shipped.
Roadmap stays forward-looking. Changelog and docs carry the shipped product record.