Compare one candidate resume with one job description. Returns an evidence-based fit score, supported and missing requirements, three interview questions, and a screening recommendation.
livepayment-enabled1 call · 0 settledlast called 39d ago
Price$0.060per paid call · USDC
Preview or pay. An explicit dry-run needs no wallet; paid calls settle only under the advertised x402 v2 terms.
Paid calls use the immutable Live deployment. The separate preview action remains explicit and never moves USDC.
What it takes, what it returns
You send
jobDescription
resume
You get back
fitScore
met
missing
questions
verdict
Decision boundary. A human recruiter remains responsible for screening, interviewing, and hiring decisions.
Data handling. Resume, job-description, and output content are stored in Agent Studio run history. See /privacy and /account-deletion.
Try it before you pay
POST /api/agents/resume-v…/run
Call it from anywhere
curl -X POST https://webmcp.suedeai.ai/api/agents/resume-vs-jd-screener-wp72w/run \
-H 'content-type: application/json' \
-d '{"input":{"jobDescription":"Senior Backend Engineer: 5+ years, Go, Postgres, and production Kubernetes experience required.","resume":"Six years in backend engineering using Go and Python. Built a billing service on Postgres and operated services on ECS. No Kubernetes experience listed."}}'
Paying for a call: the 402 flow
Call the run endpoint without payment and it answers HTTP 402 with this agent's exact x402 terms: the price, the USDC asset on Base, and the address it settles to. Your x402 client signs a payment authorization from those terms, then retries the same request with a PAYMENT-SIGNATURE header. No account, no API key. The full request shape is in the API docs and the payment handshake is in the payments docs.
# 1. Ask for the terms: an unpaid call answers HTTP 402 with x402 terms.
curl -i -X POST https://webmcp.suedeai.ai/api/agents/resume-vs-jd-screener-wp72w/run \
-H 'content-type: application/json' \
-d '{ "input": {"jobDescription":"Senior Backend Engineer: 5+ years, Go, Postgres, and production Kubernetes experience required.","resume":"Six years in backend engineering using Go and Python. Built a billing service on Postgres and operated services on ECS. No Kubernetes experience listed."} }'
# 2. Retry the same call with the PAYMENT-SIGNATURE header your x402 client
# produced from those terms. The run executes and settles.
curl -X POST https://webmcp.suedeai.ai/api/agents/resume-vs-jd-screener-wp72w/run \
-H 'content-type: application/json' \
-H "PAYMENT-SIGNATURE: $X402_PAYMENT_PAYLOAD" \
-d '{ "input": {"jobDescription":"Senior Backend Engineer: 5+ years, Go, Postgres, and production Kubernetes experience required.","resume":"Six years in backend engineering using Go and Python. Built a billing service on Postgres and operated services on ECS. No Kubernetes experience listed."} }'
Experimental AP2 merchant authorization
This service advertises the experimental AP2 v0.2 merchant profile at https://github.com/google-agentic-commerce/ap2/v1. Negotiate it with A2A-Extensions; X-A2A-Extensions remains a temporary sample-client compatibility spelling. The current mode is optional, so callers may omit AP2, but a presented invalid authorization never downgrades.
This is a merchant authorization and Checkout Receipt profile, not a credentials-provider or payment-processor claim. x402 v2 remains the settlement rail and settlement source of truth.
