AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
Answers grounded in your records. TRUE, FALSE or UNKNOWN, with conflict detection, in-place correction and targeted deletion. See real API results.
Developer toolsJavaScriptGitHub @wendelxiaOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Proprietary hosted API for structured memory: answers questions against supplied records as TRUE, FALSE or UNKNOWN, flags conflicts, and supports in-place correction and targeted deletion.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Marvnor is a proprietary hosted API for LLM applications. Store supplied facts as source, relation and target records; ask structured questions against those records and receive TRUE, FALSE or UNKNOWN, with conflicting values flagged. Correct records in place or delete selected records. Send the current question and relevant Marvnor results to your model to write the answer.
Use it to check project dependencies, business states, time-sensitive records and conflicting information. Keep confirmed records between questions and pass only the results needed for the next answer.Read the full README ↗Marvnor is a proprietary hosted MCP server and HTTP API for agent memory and record-based verification. Store supplied facts as source, relation and target records; ask structured questions against those records and receive TRUE, FALSE or UNKNOWN, with conflicting values flagged. Correct records in place or delete selected records. Send the current question and relevant Marvnor results to your model to write the answer.
Use it to check project dependencies, business states, time-sensitive records and conflicting information. Keep confirmed records between questions and pass only the results needed for the next answer.
Create a test Key · Quickstart · API reference · Recorded demo
Create a trial Key, then connect your existing AI. Follow the quickstart for setup, the working rule and everyday examples. Five tools handle saving, retrieval, verification, correction and deletion.
https://api.marvnor.com/v1/mcpAuthorization: Bearer <MARVNOR_API_KEY>Use one Key per independent project. Your AI saves confirmed or sourced facts and queries Marvnor when it needs project memory. Tasks that do not depend on saved facts stay with your existing AI and tools. Usage test evidence.
Prefer direct HTTP? Run the Python example to save, verify, resolve a conflict, correct and delete its own test data. No SDK or dependencies are required.
Latest news, October 10: Marvnor reports stronger record-based judgments and a 98.2% input reduction in a long-history test · 中文新闻稿
Before
After
Chinese originals: Before · After.
October 10, 2026 rerun:
| Test | Result | What it demonstrates |
|---|---|---|
| Two structured record-verification sets | Marvnor: 20/20 in each. DeepSeek text answers across three runs: A 16/20 each; B 14/20, 15/20, 15/20 | More accurate judgments on the supplied records, including unknown and conflicting evidence |
| Final question after 160 turns of synthetic history | Model input: 5,328 to 95 tokens, a 98.2% reduction; both answers correct | Reusable relevant facts sharply reduce repeated model input |
| Original, shuffled and duplicated facts | 420/420 expected verdicts across seven datasets | Stable conclusions despite changes in input order and duplicate evidence |
| Saved single-value conflicts, tested locally | Both incompatible values flagged; removing one restored support for the other | Conflict management across saved records |
| Complex logic under 20 concurrent requests | Every request returned 20/20 expected verdicts; median request time 603 ms | Correct batch judgments during the measured concurrent workload |
The public suite returned 1,227/1,227 expected verdicts across 62 requests, covering input variants and repeated workloads. Read the report and every comparison question or inspect the data.
中文使用说明 · Test index and archives · News · Public materials license
Send feedback and test results to [email protected]. Keep account keys and private customer material out of feedback.
Building an agent or project-memory tool? Bring one concrete use case and try the API with your own non-sensitive sample data.