Nexscope

JEV Route (API Finder)

Find a relevant data API or content evaluation tool for a task. Call the JEV Route (API Finder) API via REST or MCP from 10 credits per call.

Cost10 credits / call
Try online
POST · https://api.nexscope.ai/jev/routeMCP · nexscope_route_api

Choose an integration method

JEV

What this API does

Find a relevant data API or content evaluation tool for a task. The request accepts intent, categorySlug. Its documented result includes candidates, catalogVersion, confidence, match.docsPath, match.endpoint, match.kind, match.mcpToolName, match.method.

JEV Route (API Finder) API use cases

Choose an API for a user request

To choose an api for a user request, a marketplace analyst submits intent and categorySlug to JEV Route (API Finder). The returned candidates, catalogVersion, confidence help identify the documented endpoint matching the user request.

Resolve an ambiguous tool request

A marketplace analyst uses JEV Route (API Finder) with intent and categorySlug to resolve an ambiguous tool request. The returned candidates, catalogVersion, confidence help ask for the missing detail before choosing a tool.

Prepare a verified integration route

For this workflow, a marketplace analyst calls JEV Route (API Finder) with intent and categorySlug to prepare a verified integration route. The result helps collect required inputs before invoking the selected API.

JEV Route (API Finder) API FAQ

What does the JEV Route (API Finder) API return?

Find a relevant data API or content evaluation tool for a task. The documented output includes candidates, catalogVersion, confidence, match.docsPath, match.endpoint, match.kind, match.mcpToolName, match.method. It corresponds to the supplied intent, categorySlug. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the JEV Route (API Finder) API cost?

The current documented cost is 10 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the JEV Route (API Finder) API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/jev/route with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_route_api. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/jev/route
MCP method
nexscope_route_api

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx
Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/jev/route

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/jev/route' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "categorySlug": "amazon-marketplace-intelligence",
  "intent": "Fetch Amazon product reviews by ASIN so I can analyze customer pain points"
}'

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

CodeDescription
200HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI execution or upstream service failed.
POSThttps://api.nexscope.ai/jev/route

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/jev/route
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
intentstringrequired
One routing intent. It is used only for discovery and is never converted into API or evaluation input.
Example: Fetch Amazon product reviews by ASIN so I can analyze customer pain points
categorySlugstringoptional
Optional current public catalog category, or jev-evaluation to limit discovery to the fixed presets.
Example: amazon-marketplace-intelligence

Code example

{
  "categorySlug": "amazon-marketplace-intelligence",
  "intent": "Fetch Amazon product reviews by ASIN so I can analyze customer pain points"
}

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

{
  "code": 0,
  "data": {
    "candidates": [],
    "catalogVersion": "<catalog version>",
    "confidence": 0.91,
    "match": {
      "docsPath": "/api-docs/amazon-reviews-list?view=api",
      "endpoint": "/api/skill-api/v1/skills/amazon-reviews-list/run",
      "kind": "skill_api",
      "mcpToolName": "nexscope_amazon_reviews_list",
      "method": "POST",
      "name": "Amazon Reviews List",
      "schemaEndpoint": "/api/skill-api/v1/skills/amazon-reviews-list",
      "slug": "amazon-reviews-list"
    },
    "models": [
      "<resolved model>"
    ],
    "policyVersion": "jev-routing-v2",
    "reason": "matched",
    "status": "matched"
  },
  "msg": "success"
}

Response fields

Nexscope response envelope. The router returns trusted metadata and never executes the matched API or evaluation preset.

NameTypeRequiredDescription
codeintegerrequired
Zero on success; non-zero for validation, access, quota, or availability errors.
dataobjectrequired
For matched, call the returned endpoint separately after collecting its required fields. For ambiguous, ask the user to clarify and route again. For no_match, do not invent or execute a capability.
data.candidatesarrayrequired
Up to three clarification candidates for an ambiguous result.
data.candidates[]objectrequired
Item in data candidates.
data.catalogVersionstringrequired
Catalog timestamp used for this routing decision.
data.confidencenumber | nullrequired
Confidence value used by this API operation.
Minimum: 0
Maximum: 1
data.matchanyrequired
Match value used by this API operation.
data.modelsarrayrequired
Resolved model versions used by the routing stages.
data.models[]stringrequired
Item in data models.
data.policyVersionstringrequired
Server-owned routing policy version.
data.reasonstringrequired
Reason value used by this API operation.
Allowed: matched, clarification_required, no_supported_api
data.statusstringrequired
Status value used by this API operation.
Allowed: matched, ambiguous, no_match
msgstringrequired
Response message.

Published data API match

NameTypeRequiredDescription
data.matchobjectrequired
Match value used by this API operation.
data.match.docsPathstringrequired
Docs path value used by this API operation.
data.match.endpointstringrequired
Endpoint value used by this API operation.
data.match.kindstringrequired
Kind value used by this API operation.
Constant: skill_api
data.match.mcpToolNamestringrequired
Mcp tool name value used by this API operation.
data.match.methodstringrequired
Method value used by this API operation.
Constant: POST
data.match.namestringrequired
Name value used by this API operation.
data.match.schemaEndpointstringrequired
Schema endpoint value used by this API operation.
data.match.slugstringrequired
Slug value used by this API operation.

Fixed JEV use-case match

NameTypeRequiredDescription
data.matchobjectrequired
Match value used by this API operation.
data.match.docsPathstringrequired
Docs path value used by this API operation.
data.match.endpointstringrequired
Endpoint value used by this API operation.
data.match.kindstringrequired
Kind value used by this API operation.
Constant: jev_use_case
data.match.mcpToolNamestringrequired
Mcp tool name value used by this API operation.
data.match.methodstringrequired
Method value used by this API operation.
Constant: POST
data.match.namestringrequired
Name value used by this API operation.
data.match.schemaEndpointstringrequired
Schema endpoint value used by this API operation.
data.match.schemaPointerstringrequired
Schema pointer value used by this API operation.
data.match.useCasestringrequired
Use case value used by this API operation.

One of option 3

NameTypeRequiredDescription
data.matchnullrequired
Null for ambiguous and no_match responses.

Responses

CodeDescription
200HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI execution or upstream service failed.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json
Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_route_api",
    "arguments": {
      "categorySlug": "amazon-marketplace-intelligence",
      "intent": "Fetch Amazon product reviews by ASIN so I can analyze customer pain points"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

10 credits / callAPI usage records

Try it

Send a real request with the same contract shown in the reference.

Endpoint
/jev/route
MCP method
nexscope_route_api
cURL
curl -X POST \
  https://api.nexscope.ai/jev/route \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "categorySlug": "amazon-marketplace-intelligence", "intent": "Fetch Amazon product reviews by ASIN so I can analyze customer pain points" }'
Response
No response yet. Run the request to see the response here.

Related APIs