Repository navigation
feat(services): add HubVibe - #1035
Open
Its-fortunatefolly wants to merge 1 commit into
Open
Its-fortunatefolly wants to merge 1 commit into
Its-fortunatefolly wants to merge 1 commit into
Conversation
|
@Its-fortunatefolly is attempting to deploy a commit to the Tempo Team on Vercel. A member of the Team first needs to authorize it. |
|
Thanks for submitting a service to the MPP directory! Complete the service pull request template in your PR description before review. It contains the current submission requirements and review criteria. |
🔀 Changed Services✅ Added
|
Its-fortunatefolly
force-pushed
the
add-hubvibe
branch
from
October 2, 2026 16:32
3e0d39b to
9eff67c
Compare
Its-fortunatefolly
force-pushed
the
add-hubvibe
branch
from
October 7, 2026 05:10
9eff67c to
48a9086
Compare
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.
Motivation
HubVibe is a pay-per-call tool node for AI agents. One origin serves 67 tools plus 5 site audits (72 paid routes): web search and cited research, email verification, company enrichment, KYC and sanctions screening, stock prices, SEC filings and insider trades, crypto and prediction-market odds, news in any language, economic and open data, speech, image and video generation, and sandboxed Python. Each tool is one POST route at a fixed per-call price, with a published request schema, example and typed 200 response schema. A result that fails its published schema is not delivered and not charged.
Summary
schemas/services.ts.pnpm generate:discoverysucceeds. (Passed locally on the previous revision; not re-run on this one.)pnpm check:typespasses. (Passed locally on the previous revision; not re-run on this one.)pnpm buildsucceeds. (Passed locally on the previous revision; not re-run on this one.)Update 2026-10-07: rebased on
mainat #1055 and brought up to the live service: 72 routes (addsPOST /work/agent/task,/work/agent/task_pro,/work/agent/task_maxand/work/lead/qualify, same entry shape as the rest). Each of the 72 listed routes was probed unpaid against https://hubvibe-io.com with its request example: every one answers HTTP 402 with a Tempochargechallenge whose amount matches the listing (72 of 72). No live paid route is missing and none is listed that isn't live. Homepage,llms.txt,openapi.jsonand the icon all return 200.Key design considerations
charge, at a fixed price per call. An unpaid request gets HTTP 402 withWWW-Authenticate: Payment(methodtempo, realmhubvibe-io.com). The same routes also accept MPPevmand x402; this entry lists Tempo only.GET /work/receipts/{id}) and a pre-purchase contract check (GET /contracts/{capability}).🤖 Generated with Claude Code