# Eden AI vs Nemotron 3.5 Super VL (slim)

> Eden AI and Nemotron 3.5 Super VL score within a point of each other for llm inference, 59.9 and 59.3 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/eden-ai-vs-nemotron-3-5-super-vl.md (~6,850 tokens) · this version ~3,280 tokens · JSON https://www.anchorterminal.com/compare/eden-ai-vs-nemotron-3-5-super-vl.json · canonical https://www.anchorterminal.com/compare/eden-ai-vs-nemotron-3-5-super-vl
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Eden AI and Nemotron 3.5 Super VL score within a point of each other on agent readiness, 59.9 (C) and 59.3 (C). Nemotron 3.5 Super VL leads on reliability, payments & pricing and maintenance & community. Both do llm inference.

- Eden AI: C 59.9, rank #675 of 1510 · https://www.anchorterminal.com/tools/eden-ai.min.md
- Nemotron 3.5 Super VL: C 59.3, rank #708 of 1510 · https://www.anchorterminal.com/tools/nemotron-3-5-super-vl.min.md
- Eden AI, good for Teams that want one key and bill for many LLMs plus OCR, speech, translation and web tools, with EU-only processing. Ahead on Schema & documentation, 81 against 74; Agent ergonomics, 75 against 65; Security & auth, 82 against 54.
- Nemotron 3.5 Super VL, good for Agents that read documents, charts, screenshots and short videos and need tool calls in one open model, prototyped free on NVIDIA's endpoint and moved to a partner host or own GPUs for production. Ahead on Reliability, 58 against 33; Payments & pricing, 35 against 30; Maintenance & community, 71 against 58. Also Free to start without a card.

| Category | Eden AI | Nemotron 3.5 Super VL |
| --- | --- | --- |
| Reliability (16%) | 33 | 58 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 74 |
| Agent ergonomics (13%) | 75 | 65 |
| Security & auth (14%) | 82 | 54 |
| Payments & pricing (10%) | 30 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 58 | 71 |
| Transparency & trust (7%) | 55 | 58 |

| Fact (where they differ) | Eden AI | Nemotron 3.5 Super VL |
| --- | --- | --- |
| Kind | Model router | Model API |
| Vendor | Eden AI SAS | NVIDIA |
| Hosted endpoint | `https://mcp.edenai.run/mcp` | `https://integrate.api.nvidia.com/v1` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Pricing | Pay per use | Free |
| Licence | none | OpenMDW-1.1 for the weights (permissive, not an OSI licence). The hosted trial endpoint is under the NVIDIA API Trial Terms of Service, and the NIM container under the NVIDIA Software Licence Agreement |
| Last release | 2026-11-05 | 2026-10-15 |
| Terms last updated | 2026-10-22 | not read yet |
| Privacy policy last updated | 2026-10-22 | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Security & auth, Eden AI +28: Eden AI 82 (Router, read on the model lines. Bearer keys with per-key budgets, expiry and attribution, a key management API, and deny-by-default guardrails that limit models per member, role or key (25). The data retention page says request and response content isn't stored and data isn't used to train models by default (18). Content logging is opt-in, async results are deleted after 7 days, and an organisation can enforce Zero Data Retention and region rules; the EU endpoint refuses non-EU models with 451 (13). Cost and provider per response, and a monitoring dashboard by key (12). The security page says Eden AI is SOC 2 and ISO 27001 certified and links a trust centre; /.well-known/security.txt returns 404 and no disclosure policy was found (14). 25+18+13+12+14 = 82.); Nemotron 3.5 Super VL 54 (Model reading. `nvapi-` bearer keys sent in a header. NVIDIA's NGC docs say personal keys are limited to the services and role chosen at creation and take an expiry, and service keys can be scoped to actions (25 of 30). Inference only, with no write operation, but no zero-retention option for the hosted trial was found, and the model page asks callers not to send confidential or personal data (8 of 20). The model reads web pages, PDFs and images an agent passes it, and NVIDIA publishes safety, bias and privacy subcards, but no prompt-injection guidance or results were found (5 of 15). No per-call log for API callers was found, only rate limits shown in the account (3 of 15). NVIDIA PSIRT runs coordinated disclosure and publishes security bulletins, linked from the card, the reading nvidia-nemo-retriever and nemo-guardrails give the same programme (13). www.nvidia.com/.well-known/security.txt answered 403 per the 2 November check and build.nvidia.com has none, and no certification or bug bounty for the API catalogue was found (13 of 20). 25+8+5+3+13 = 54.)
- Reliability, Nemotron 3.5 Super VL +25: Eden AI 33 (Router, read on the hosted lines. No status page is linked from the site or docs, and status.edenai.co didn't resolve for us on 6 November 2026 (0). No incident history to read (5). The rate-limits page gives 10 requests a second per account, shared across keys, while the plans page gives 7 a second, raisable to 15, so the figure is documented but inconsistent (10). Fallback retries the next model or provider on a 429 or error inside one request, but no client-facing 429 or Retry-After guidance was found (8). No SLA published; 'Dedicated support & SLA' is listed only for the custom Advanced plan, and the pricing page's '99.99%' uptime is a claim without a status page behind it (0). The v3 API is GA (10). 0+5+10+8+0+10 = 33.); Nemotron 3.5 Super VL 58 (Hosted reading, for NVIDIA's trial endpoint. status.ngc.nvidia.com is a Statuspage site with NVIDIA Build and Cloud Functions components and a readable history (20). In the 90 days to 4 November, re-read from history.atom, two incidents, both minor for an API caller, and none posted since 29 September. SMS verification for NVIDIA Build was unavailable in China from 23 to 29 September, which affects sign-up, and on 10 August new Cloud Functions deployments failed for about three hours while existing deployments kept running (20). build.nvidia.com gives limits of up to 40 requests a minute and 10,000 a day, and says they vary by model and with other users' traffic (12 of 15). The OpenAPI file documents a 202 pending result with an `NVCF-REQID` to poll, but no 429, Retry-After or backoff guidance, and NVIDIA's FAQ says to expect long waits under load (3 of 15). No SLA for the trial. NVIDIA's SLAs come with AI Enterprise for self-hosted software (0). The card says v1.0 GA, but the hosted page calls the model early access and NVIDIA calls the catalogue a trial for prototyping only (3 of 10). The model page re-read on 4 November still says early access, with a free endpoint marked available and 40 rpm. 20+20+12+3+0+3 = 58.)
- Maintenance & community, Nemotron 3.5 Super VL +13: Eden AI 58 (Closed service, read on the model lines. The docs repository changed on 5 and 6 November 2026, including retiring Nova Reel and Veo from video generation, and the terms were updated 22 October (30). No public changelog, so dated API changes in the last 90 days come only from docs commits (12 of 20). Chat support within 48 working hours, no public changelog (8). No SDK of its own, and the MCP server isn't in the official MCP registry (5). Nothing to judge package health by beyond the docs repository (3). 30+12+8+5+3 = 58.); Nemotron 3.5 Super VL 71 (Released on 15 October 2026. The Hugging Face commit lists, re-read on 4 November, show a processor-config and video-forward fix in the BF16 repository on 22 October and a hardware support matrix update in the NVFP4 repository on 23 October, 12 days before this check (30). NVIDIA released three Nemotron 3.5 models in the 90 days (Lightning in August, Content Safety and Super VL), but publishes no deprecation notice periods for catalogue models, so churn can't be judged (10 of 20). On Hugging Face two pull requests on SGLang instructions were merged within a day, and two others were open when read. Support for the free tier is the developer forum (15 of 25). NVIDIA maintains `langchain-nvidia-ai-endpoints` (1.5.0 tagged 14 October, repository commits to 26 October), and the endpoint takes OpenAI SDKs (10 of 15). Day-one recipes for vLLM 0.32.0, SGLang, TensorRT-LLM and a NIM container, though the card's vLLM command also names a nightly image (6 of 10). 30+10+15+10+6 = 71.)
- Agent ergonomics, Eden AI +10: Eden AI 75 (Router, read on the model lines. Chat completions, Responses and an Anthropic Messages route in the OpenAI shape, with tool calling depending on the routed model (14 of 20) and structured output likewise (10 of 15). Caching is named in the terms as part of the service, without a per-model price table we read (8 of 15). Context depends on the model; the keyless /v3/models catalogue lists capabilities, prices and regions per model so an agent can choose (12 of 15). A Batches API (10 of 10). No SDK of its own; the docs use the OpenAI Python and TypeScript SDKs, and a hosted MCP server exposes about 40 expert-model tools plus upload_file, check_job and list_models (21 of 25). 14+10+8+12+10+21 = 75.); Nemotron 3.5 Super VL 65 (Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). OpenAI-format tools, `tool_choice` auto, none, required or a named function, and parallel calls on by default (20 of 20). `response_format` with `json_schema` and `strict` in the OpenAPI file. Not tested by us (12 of 15). The card describes prefix caching for self-hosted serving, but no caching on the hosted endpoint is documented (2 of 10). 1M tokens in the weights, but the hosted page lists 262K, and completions are capped at 131,072 tokens (12 of 15). No batch mode (0 of 10). Any OpenAI SDK works with the base URL, and NVIDIA maintains `langchain-nvidia-ai-endpoints`. Only `messages` is required, but reasoning defaults to on at high effort and the reference defaults `stream` to true (10 of 15). Errors carry a message, type and request id, with no 429 or rate-limit body documented (9 of 15). 65.)
- Schema & documentation, Eden AI +7: Eden AI 81 (Router, scored on the API lines. OpenAPI 3.1 document for v3 (version 3.0.0, 46 paths) at api.edenai.run/v3/docs/openapi.json, plus a management API spec (25). llms.txt on the site and in the docs, llms-full.txt and Markdown pages (10). llms.txt states when to use Eden AI and when not to, and the docs separate chat models from expert models (17). Requests follow the OpenAI shape, and expert-model tools on the MCP server carry JSON Schema inputs (12). Examples throughout, but the spec documents only 200, 201, 202, 302 and 422, while llms.txt names 401 and 451 for region refusals (10). Versioned /v3 path, but no public changelog was found (7). 25+10+17+12+10+7 = 81.); Nemotron 3.5 Super VL 74 (Model reading. An OpenAPI 3.1 file for this model's `/chat/completions` on docs.api.nvidia.com, with typed request and response schemas (25). build.nvidia.com/llms.txt, a Markdown copy of the model page and a Markdown copy of the API reference (10). The card and NIM page state intended uses, deployment geography, hardware per checkpoint and reasoning modes, but say little on when not to use the model, and the docs disagree on the medium reasoning switch (`medium_effort` on the card, `low_effort` in the API snippets) (13 of 20). Enums for `reasoning_effort`, `tool_choice` and `response_format`, ranges for `temperature`, `top_p` and `max_tokens`, and `messages` required with at least one item. `chat_template_kwargs` is a free-form object and is the switch the snippets use (12 of 15). Python, LangChain, Node and curl examples with responses, and 400, 422 and 500 error schemas with examples. No 429 (11 of 15). No changelog for the catalogue or the model. The OpenAPI version is 1.0.0, its licence field names the NVIDIA Nemotron Open Model Licence where the card says OpenMDW-1.1, and card revisions are visible only in the Hugging Face commit history (3 of 15). 74.)
- Payments & pricing, Nemotron 3.5 Super VL +5: Eden AI 30 (No x402, MPP or L402 (0). Provider prices with no markup plus a 5.5% platform fee, published per model in the keyless catalogue (20). llms.txt says some models are billed $0 for tests, but whether a new account can call them without buying credits isn't stated (10). A person signs up in a browser and buys credits through Stripe (0). 0+20+10+0 = 30.); Nemotron 3.5 Super VL 35 (No x402, MPP or L402 (0). The hosted endpoint is free and says so without a login, and the production routes are priced in public (AI Enterprise at $4,500 a GPU a year, partner hosts per million tokens), but the free endpoint can't be used in production and has no per-call price of its own (15 of 20). Free with no card per build.nvidia.com/llms.txt (20). A person signs in at build.nvidia.com, which uses SMS verification per the status page, to generate a key. No keyless or programmatic route (0). 35.)
