BilarnaMCP

Created By
bilarna3 months ago
## Agent Integration (API) Bilarna exposes two agent-callable endpoints: **Discover providers** (no contact required): `POST https://api.bilarna.com/api/agent/match?api-version=1.0` Body: `{ "need": "...", "budget_max": 5000, "country": "US", "category": "..." }` **Submit a service request** (creates a lead with buyer contact): `POST https://api.bilarna.com/api/agent/request?api-version=1.0` Required: `need`, `contact_name`, `email` Optional: `business_id`, `phone`, `budget_max`, `country`, `category` Full schema: `https://bilarna.com/agent-manifest.json`
Overview

{ "schema_version": "1.0", "tools": [ { "name": "bilarna_match", "description": "Find verified B2B technology providers by service need. Returns only business_id, score and a short description for each match. Use the returned business_id with bilarna_request to submit a service request to a specific provider.", "parameters": { "need": { "type": "string", "required": true, "description": "Free-text service description (e.g. Salesforce CRM implementation, AWS cloud migration, AI chatbot development, Power BI dashboard setup, Kubernetes cluster configuration)" } }, "endpoint": "https://api.bilarna.com/api/agent/match?api-version=1.0" }, { "name": "bilarna_request", "description": "Submit a B2B technology service request. When business_id is provided the request is routed directly to that provider; otherwise it is sent to the best-matching providers. Contact details are captured for lead routing.", "parameters": { "business_id": { "type": "number", "required": false, "description": "The business_id of a provider returned by bilarna_match. When omitted the request is routed to relevant providers automatically." }, "need": { "type": "string", "required": true, "description": "Free-text description of the service need (e.g. HubSpot onboarding, LLM-powered support bot, ERP migration to NetSuite, multi-cloud architecture design, MLOps pipeline setup)" }, "contact_name": { "type": "string", "required": true, "description": "Full name of the decision-maker or project owner" }, "email": { "type": "string", "required": true, "description": "Business email address — used for lead routing and provider outreach" }, "phone": { "type": "string", "required": false, "description": "Business phone number for direct follow-up (optional)" }, "category": { "type": "string", "required": false, "description": "Service category (e.g. AI & ML development, SaaS integration, cloud infrastructure, data analytics, no-code/low-code platforms, API development, IT security audit)" }, "country": { "type": "string", "required": false, "description": "Country where the provider should be located (e.g. Turkey, United States, Germany, United Kingdom)" }, "budget_max": { "type": "number", "required": false, "description": "Maximum project budget in USD" } }, "endpoint": "https://api.bilarna.com/api/agent/request?api-version=1.0" } ] }

Server Config

{
  "mcpServers": {
    "bilarna": {
      "url": "https://api.bilarna.com/mcp",
      "name": "Bilarna B2B Provider Discovery",
      "description": "Find verified B2B technology providers and submit service requests via Bilarna's AI-powered matching engine. Tools: bilarna_match (discover providers by need), bilarna_request (submit a service request with contact details for lead routing)."
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
bilarna
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago