Nexscope

JEV Route API

REST API and MCP service documentation generated from server-side API definitions. Responses use the shared code, msg, and data envelope.

API selector
JEV

API overview

Routes one intent to trusted metadata for a published data API or fixed JEV preset. The routing intent is sent to TypeSafe for evaluation. Ambiguous results require clarification; routing never executes a match, generates evaluation input, or fills missing parameters. Requires an active Nexscope subscription. The JEV node does not deduct Nexscope business credits; any selected data API retains its existing billing. Route and evaluate share limits of 20 requests per user per minute, 200 requests globally per minute, and 5,000 requests globally per rolling day; each route or evaluate call counts as one request. Quota admission is sequential: per-user minute, global minute, then global rolling day; an earlier admitted counter remains incremented if a later check rejects the request.

Try this API
Endpoint
/api/skill-api/v1/jev/route
MCP method
nexscope_route_api

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 .
POST/api/skill-api/v1/jev/route

Run an API

Send a JSON request body using the parameters described below.

Slugjev-route
HeadersAuthorization: Bearer nk-...
Content-Type: application/json
Request bodyAPI-specific JSON object.
Response bodyPlatform envelope: code, msg, data, ts, time, cost, traceId. Inspect data.status for asynchronous completion.

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.

Example request

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

Run this API

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

Endpoint

MethodPOST
Path/api/skill-api/v1/jev/route
AuthBearer API key
Content-Typeapplication/json

Request body

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 four fixed presets.
Example: amazon-marketplace-intelligence

Request example

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

Response body

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.
msgstringrequired
Response message.
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.statusstringrequired
Status value used by this API operation.
Allowed: matched, ambiguous, no_match
data.catalogVersionstringrequired
Catalog timestamp used for this routing decision.
data.policyVersionstringrequired
Server-owned routing policy version.
data.modelsarrayrequired
Resolved model versions used by the routing stages.
data.models[]stringrequired
Item in data models.
data.confidencenumber | nullrequired
Confidence value used by this API operation.
Minimum: 0
Maximum: 1
data.matchanyrequired
Match value used by this API operation.
data.candidatesarrayrequired
Up to three clarification candidates for an ambiguous result.
data.candidates[]objectrequired
Item in data candidates.
data.reasonstringrequired
Reason value used by this API operation.
Allowed: matched, clarification_required, no_supported_api

Published data API match

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

Fixed JEV use-case match

NameTypeRequiredDescription
data.matchobjectrequired
Match value used by this API operation.
data.match.kindstringrequired
Kind value used by this API operation.
Constant: jev_use_case
data.match.namestringrequired
Name value used by this API operation.
data.match.methodstringrequired
Method value used by this API operation.
Constant: POST
data.match.endpointstringrequired
Endpoint value used by this API operation.
data.match.mcpToolNamestringrequired
Mcp tool name value used by this API operation.
data.match.useCasestringrequired
Use case 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.docsPathstringrequired
Docs path value used by this API operation.

One of option 3

NameTypeRequiredDescription
data.matchnullrequired
Null for ambiguous and no_match responses.

Response example

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

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

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.

Related APIs

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/api/skill-api/v2/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.

Call a tool

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

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

GET / POST /api/skill-api/v1/mcp

Online test

Execute the current API with your API key and JSON payload.

Pricing pendingAPI usage records

Try it

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

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