passlisted in Coinbase#3 by calls of 6 on this host
0.03 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 3
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-09-03 18:51 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.03 USDC
- Networks
- 2
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 29 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
TOLL files capabilities decision optimization under identity: a POST endpoint on api.vrsai.tech, listed in the Coinbase registry.
A call to capabilities decision optimization costs 0.03 USDC on Base, as declared.
The request to capabilities decision optimization is a json body with the fields lanes, demands, sources, objective and problem_type.
For capabilities decision optimization the listing declares 2 accepts on Base and Solana, to 2 different wallets.
capabilities decision optimization returns json; the example shows status, quality, decision, evidence, economics, diagnostics and 2 others.
capabilities decision optimization answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
capabilities decision optimization is one of 6 listed endpoints on api.vrsai.tech, tied 3rd by calls with 3 others among them.
capabilities decision optimization takes 14% of the calls counted across api.vrsai.tech.
Over 30 days: 3 calls, 2 payers.
capabilities decision optimization was last called 12 days before the snapshot.
Closest in price to capabilities decision optimization within identity: address risk at vibesprings.net and company research at lionx402.com.
Among comparable prices in identity, capabilities decision optimization sits above 75% of them.
Across identity, 1,501 endpoints carry counters and capabilities decision optimization out-counts 69% of them.
Its payee wallet receives for 6 listed endpoints on one host.
The seller's tags on capabilities decision optimization are decision-optimization, resource-allocation, assignment-optimization and constrained-selection.
Exactly this price appears on 51 other listings in identity.
the payment options, as of 2026-09-15 21:20 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.03 USDC | exact | 0x6746dF…bA09Af |
| Coinbase | solana: | USDC | 0.03 USDC | exact | EiJRESZj…4xFocj |
the checks, as of 2026-09-15 06:04 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 06:04 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:35 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 05:29 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:46 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 11:37 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-03 18:51 UTC · method · live
The input and output block
{
"input": {
"body": {
"lanes": [
{
"demand_id": "warehouse_1",
"source_id": "supplier_a",
"unit_cost": "2"
},
{
"demand_id": "warehouse_1",
"source_id": "supplier_b",
"unit_cost": "5"
}
],
"demands": [
{
"id": "warehouse_1",
"requirement": "80",
"satisfaction": "exact"
}
],
"sources": [
{
"id": "supplier_a",
"capacity": "100"
},
{
"id": "supplier_b",
"capacity": "100"
}
],
"objective": "minimize_total_cost",
"problem_type": "allocation"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"status": "OPTIMAL",
"quality": {
"best_bound": "160",
"absolute_gap": "0",
"relative_gap": "0",
"solver_optimality": "optimal_within_profile_tolerance",
"solution_uniqueness": "unknown",
"semantic_feasibility_verified": true
},
"decision": {
"lanes": [
{
"quantity": "80",
"demand_id": "warehouse_1",
"source_id": "supplier_a"
},
{
"quantity": "0",
"demand_id": "warehouse_1",
"source_id": "supplier_b"
}
],
"problem_type": "allocation",
"source_activations": [
{
"active": true,
"source_id": "supplier_a"
},
{
"active": false,
"source_id": "supplier_b"
}
]
},
"evidence": {
"solver": "highs",
"solver_version": "1.15.2",
"ruleset_version": "decision_optimization_r1",
"input_fingerprint": "v1:23bf4e29934aad481275e4bf38cb45617bbbe664ad3dd5d771af2fe3d4d1c938",
"model_fingerprint": "v1:392d8ab317c91b7339a92c2b9fa4b2b30f326f2175955d6fa362c4b57287c5a5",
"constraints_checked": 3,
"constraints_violated": 0,
"decision_fingerprint": "v1:43b9ac81c64b8f95e46837a5103ac13d8f27ad829b32ee06463079bf0be83b81"
},
"economics": {
"sense": "minimize",
"objective": "minimize_total_cost",
"objective_value": "160"
},
"diagnostics": {
"binding_constraints": []
},
"problem_type": "allocation",
"machine_action": "CONSUME_OPTIMAL_DECISION"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 21:20 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "capabilities decision optimization on api.vrsai.tech", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/api-vrsai-tech-v1-capabilities-decision-optimization-a1fce8/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-api-vrsai-tech-v1-capabilities-decision-optimization-a1fce8-2026-09-15T21-20Z,
author = {TOLL},
title = {capabilities decision optimization on api.vrsai.tech},
howpublished = {\url{https://tollindex.com/e/api-vrsai-tech-v1-capabilities-decision-optimization-a1fce8/at/2026-09-15T21-20Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 21:20 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.