Repository navigation
Poppy: one public deployment exists (salespeak.ai) - #6
Open
omergotlieb wants to merge 1 commit into
Open
omergotlieb wants to merge 1 commit into
omergotlieb wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@omergotlieb is attempting to deploy a commit to the Era AI Labs Team on Vercel. A member of the Team first needs to authorize it. |
4 tasks done
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Disclosure: I work at Salespeak. This corrects a claim about our own deployment, so please check it yourself before merging.
What changed
The Poppy page says no company is publicly known to serve a working
poppy.json. salespeak.ai has served one since October 10, 2026. This updatesreality_checkandstatus_note, and movesstatusfromdrafttoearly.Sources
The deployment is its own primary source:
It returns a Draft 0.1 discovery document:
protocol_version,organization,auth.issuer, and an agent entry of typepoppywith a conversations endpoint. The issuer's OAuth metadata is at/.well-known/oauth-authorization-serveron the issuer host. It lists thejwt-bearergrant,private_key_jwtclient authentication, DPoP, and Client ID Metadata Documents.Public write-up: https://salespeak.ai/agent-endpoint/
The limits, stated plainly
On the status change
Your rule for "Early use" is "some real, public deployments, but small or still in trials." One deployment, by a company that is not a launch partner, with no outside traffic, is the smallest case of that.
If you would rather keep "Draft" until a second deployment or a launch partner ships, I am happy to drop the
statusline and keep only thereality_checkfix. That sentence is out of date either way.Checklist
status, the evidence meets the rules incontent/contribute.md. (Borderline; see above.)last_verifiedon pages where I rechecked every claim. (Not changed: I rechecked this one claim only.)🤖 Generated with Claude Code