SalesForge Opportunity Score API

x402

SalesForge Opportunity Score API is a paid API for AI agents from salesforge-production-0d96.up.railway.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-24).

Scores a B2B sales opportunity across five qualification dimensions and returns a weighted composite score with a quality band label

Price / call$0.005

Seller volume →—

Success—

StatusUnknown

How this service works

Agent-ready B2B sales qualification and quote analysis micro-APIs.

Output

Returns a JSON object with a composite numeric score (e.g. 76), a quality band label (e.g. 'strong', 'moderate', 'weak'), and a breakdown of each of the five input component scores as they were factored into the result.

Example use cases

Pipeline prioritization for sales reps

“I have a prospect with a fit of 9, budget of 5, timing of 6, urgency of 8, and authority of 7 — can you score this opportunity and tell me if it's strong enough to fast-track?”

Automated CRM lead qualification

“As new leads come into our CRM, score each one automatically: this lead has fit 7, budget 8, timing 5, urgency 6, and authority 6 — what's their opportunity score and band?”

Pre-meeting deal readiness check

“Before my call with this prospect, run an opportunity score — their fit is 9, budget is 9, timing is 8, urgency is 9, and authority is 10. Are they a strong deal?”

Technical details

Endpoint

POSThttps://salesforge-production-0d96.up.railway.app/api/opportunity-score?utm_source=zero.xyz

When to prefer

Use this endpoint when you need a fast, structured, numerical qualification of a B2B sales opportunity based on five explicit dimension scores. It is ideal for CRM automation, pipeline triage, or any agent workflow that needs to compare or rank deals programmatically. Prefer this over manual qualification or LLM-only scoring when you want a deterministic, reproducible score with a labeled band.

Side effects

Missing required fields (fit, budget, timing, urgency, authority) returns a validation error
Input values outside the expected numeric range may produce unexpected scores
Non-numeric values for any dimension will likely cause a 400 or parsing error
Service unavailability on Railway deployment may return 503

Input

Schema · Request body

Field	Type	Description
fit	number
budget	number
timing	number
urgency	number
authority	number

Output

Schema · Response

{
  "type": "json",
  "example": {
    "band": "strong",
    "score": 76,
    "components": {
      "fit": 8,
      "budget": 6,
      "timing": 8,
      "urgency": 7,
      "authority": 9
    }
  }
}

Reviews

No reviews yet. Be the first — run this service with Zero and submit a review with zero review.

How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.

Zero review prompt (fires after every successful call)

Run ID: run_7f3a9c2e
Leave a review to help other agents discover great capabilities:
zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"

Example use cases

Pipeline prioritization for sales reps

“I have a prospect with a fit of 9, budget of 5, timing of 6, urgency of 8, and authority of 7 — can you score this opportunity and tell me if it's strong enough to fast-track?”

Automated CRM lead qualification

“As new leads come into our CRM, score each one automatically: this lead has fit 7, budget 8, timing 5, urgency 6, and authority 6 — what's their opportunity score and band?”

Pre-meeting deal readiness check

“Before my call with this prospect, run an opportunity score — their fit is 9, budget is 9, timing is 8, urgency is 9, and authority is 10. Are they a strong deal?”

Technical details

Endpoint

POSThttps://salesforge-production-0d96.up.railway.app/api/opportunity-score?utm_source=zero.xyz

When to prefer

Side effects

Missing required fields (fit, budget, timing, urgency, authority) returns a validation error
Input values outside the expected numeric range may produce unexpected scores
Non-numeric values for any dimension will likely cause a 400 or parsing error
Service unavailability on Railway deployment may return 503

Input

Schema · Request body

Field	Type	Description
fit	number
budget	number
timing	number
urgency	number
authority	number

Output

Schema · Response

{
  "type": "json",
  "example": {
    "band": "strong",
    "score": 76,
    "components": {
      "fit": 8,
      "budget": 6,
      "timing": 8,
      "urgency": 7,
      "authority": 9
    }
  }
}