Discover AI Applications

Browse applications built on modern technologies. Explore PoC and MVP applications created by our community and discover innovative use cases for modern technologies.

Agent_Trap_Evals

Agent_Trap_Evals

The problem: agents rarely fail hard questions. They fail chores. They report "backup verified" because the log says success, while the archive is truncated. These false claims slip out during routine work, and a real shell makes them dangerous. What Receipts does: you give it a real task, like checking a backup or triaging a failing build. A control layer plans the work and runs every action in an isolated Vultr sandbox [gVisor pods on VKE]. The sandbox has no secrets, has time and memory caps, and is destroyed after each task. Every command's output, exit code, and files become a receipt. Before any claim reaches you, a verifier checks it against those receipts: did the agent check the layer that matters, or just the easy one? An unsupported claim is blocked and sent back to be verified, or reported as unverified. You get the answer together with its proof. Containment: [demo moment, e.g. the agent runs rm -rf / and the sandbox absorbs it; the host is untouched]. Measured: we score Receipts with agent-trap-evals, an open-source trap set we built before the hackathon from real agent incidents. Verifier off vs. on: [X/Y vs. X/Y caught], [n] false alarms on honest controls. For: platform and DevOps teams putting agents on operational work, where a confident false "done" costs more than a slow answer. Sandboxes like E2B contain actions but don't check claims. Eval tools score offline but don't stop a bad claim at runtime. Receipts does both, live. [Business model; next steps.] All LLM calls use Vultr Serverless Inference.

AITeCXO
AgentOpsAnthropic ClaudeAWS+11
Trifecta Checker AI Safety Gate for Lethal Agents

Trifecta Checker AI Safety Gate for Lethal Agents

Trifecta Checker is an AI safety gate that blocks Lethal Trifecta attacks - the dangerous combination of Private Data + Untrusted Content + External Communication that enables data theft via prompt injection. The problem: AI agents with tools like read_gmail, browse_web, and send_email can be tricked by malicious web content to steal private emails and exfiltrate them. This is called the Lethal Trifecta. Our solution: One API call - POST /api/check-trifecta - analyzes the agent's tool manifest and returns instant verdict: - LETHAL (3/3 tools): 403 Forbidden - BLOCKED - Cannot execute - WARNING (2/3 tools): 200 OK with caution flag - SAFE (1/3 tools): 200 OK - Safe to proceed Live and tested: https://trifecta-checker.vercel.app/ - LETHAL test [read_gmail, browse_web, send_email] -> 403 - WARNING [browse_web, send_email] -> 200 warning - SAFE [read_gmail] -> 200 safe For 【entity-AMD¦canonical_name=AMD】 AI League Match 4 - Intelligent Web Information Retrieval - we extend with Trusted Source Verification: before allowing external communication, we verify web sources are trusted (.gov, .edu, Concordium ID verified). If source is untrusted, block or flag. Tech: Next.js 14 + TypeScript, Vercel Edge, Python/JS SDKs, 【entity-AMD¦canonical_name=AMD】 ROCm ready for LLM inference. GitHub: github.com/altima261/trifecta-checker. Blog: dev.to/altima261. Built by Mohammed Binashwan (altima261) from Jeddah, Saudi Arabia. Team trifecta-checker solo UTC+3. This project also registered in Concordium Trusted Agents (ZK Proofs + on-chain audit) and Vultr Agent Rush (Blast Radius Zero sandbox).

trifecta-checker
VercelAMD ROCm
AMD Volta: Intelligent Web Retrieval Agent

AMD Volta: Intelligent Web Retrieval Agent

AMD Volta is an autonomous multi-hop web retrieval and synthesis engine engineered for technical research and hardware benchmarking, built for AMD AI League Match 4. Key Innovations Solved: 1. Deep DOM Table Extraction: Real hardware benchmarks live inside HTML <table> tags. Standard text chunkers flatten them into noise. Our DOM parser converts nested HTML tables into intact, atomic GitHub-flavored Markdown tables, preserving comparison matrices and bandwidth specs. 2. Resilient Multi-Engine Cascading: External search APIs fail under rate limits. Volta cascades seamlessly across DuckDuckGo API, DuckDuckGo Lite, Wikipedia, and ArXiv with user-agent rotation to eliminate unhandled crashes. 3. Hybrid BM25 & Semantic Reranking: Combines mathematical Okapi BM25 keyword matching with dense semantic similarity and deduplication. 4. Autonomous Multi-Hop Reasoning: Dynamically assesses evidence sufficiency after Hop 1, reformulates search intent, and executes Hop 2 deep retrieval when necessary. 5. Anti-Hallucination Abstention Guardrail: When queried about fictional hardware (e.g., AMD Radeon RX 19990 XTX), the agent triggers an explicit Abstention Notice, ensuring 100% factual integrity. Hardware Acceleration via AMD Instinct & ROCm: - AMD Developer Cloud (Instinct MI300X): Leverages 192GB HBM3 memory and 5.3 TB/s bandwidth to serve 70B+ LLMs via vLLM with FlashAttention-2 HIP kernels. - Local AMD ROCm: Direct GPU memory access for local embeddings and inference on Radeon / Instinct GPUs. - Universal Fallback: Zero-setup deterministic extractive engine for instant evaluation.

Deflect
AMD Developer CloudAMD ROCmStreamlit+1
NanoMesh: Local AI, Tuned to Your Hardware

NanoMesh: Local AI, Tuned to Your Hardware

NanoMesh is a Windows-first, local-first platform designed to make running AI models on personal computers simpler, smarter, and more accessible. It helps developers discover suitable models, understand hardware compatibility, and evaluate performance before committing their resources to a particular AI workload. Starting with GGUF models and llama.cpp, NanoMesh combines hardware-aware recommendations with runtime capability detection to help users determine which models are appropriate for their systems. Rather than relying solely on hardware specifications, the platform aims to distinguish verified runtime capabilities from estimates, helping users make more informed decisions about CPU and GPU execution. NanoMesh is being developed to support a practical local AI workflow: discover models, select suitable configurations, download with user approval, and benchmark performance. Its long-term goal is to compare important trade-offs, including inference speed, memory usage, stability, and task-specific model quality. AMD hardware is an important opportunity for this vision. By making runtime backends and hardware capabilities more transparent, NanoMesh aims to help developers explore local AI workloads on compatible AMD-powered systems and make better use of the computing resources they already own. The broader mission is to bring AI closer to users through efficient, hardware-aware, privacy-conscious local inference, reducing unnecessary dependence on cloud services while making experimentation more reproducible and accessible.

brass
Claude Code
GreYat Web Scout: grounded web retrieval

GreYat Web Scout: grounded web retrieval

GreYat Web Scout is a Match 4 agent for intelligent web information retrieval. It takes a natural-language question, with an optional start URL, and returns one exact value together with the page it came from. How it works: a language model (Qwen3-4B-Instruct, served on the AMD GPU by a resident process so each query skips the load time) first plans the lookup: search queries, likely official URLs, and package or project names. In parallel the agent queries several search engines and Wikipedia, and for "latest version" questions it reads the authoritative registries directly (PyPI, npm, GitHub releases, endoflife.date). It fetches the best pages, keeps the passages that match the question, and asks the model to extract a single value and say which passage it came from. Grounding comes first. An answer is only returned if the value appears verbatim on the cited page, so the source URL always backs up the answer. If no page confirms it, the agent returns an empty answer instead of a guess, and answers to "latest" questions are never taken from the model's memory. Version strings and numbers are normalised (v-prefixes, LTS labels, thousands separators) to match the grader. Everything runs locally on AMD ROCm with no external API keys. In development, on a 30-question set covering facts, ports, people, dates and live package versions, the pipeline answered 26 correctly (tested with a hosted stand-in model, since GPU time was not available).

GreYat
AMD ROCmQwen3HuggingFace Hub
SourceCourt Exact Lite

SourceCourt Exact Lite

SourceCourt Exact Lite is a bounded, evidence-first research assistant built for AMD AI League Match 4. It answers source-grounded questions while refusing to invent certainty when the available evidence does not support an exact answer. The system retrieves and parses bounded HTTP/HTTPS sources, interprets a user’s question, identifies relevant evidence, ranks candidate passages and links, and extracts an exact answer only when the evidence is sufficient. When the answer is ambiguous, unsupported, or unverifiable, SourceCourt refuses rather than fabricating a result. The project was hardened against unsafe retrieval behavior. Its transport layer rejects private and loopback network targets, protects against SSRF and DNS rebinding, preserves TLS hostname verification, limits redirects, constrains response size and timing, and avoids unsafe proxy behavior. It also includes bounded resource use, deterministic error handling, citation checks, and explicit ambiguity/refusal behavior. SourceCourt Exact Lite is packaged as a real command-line product. It can be installed as a Python package, run locally, or executed from a container image. The public release includes reproducible setup instructions, a deterministic demo, and a security-focused test suite. The release is provider-neutral at the model-adapter boundary, keeping retrieval, ranking, evidence extraction, citation, refusal, and safety logic independent from any single model provider while allowing the official Match 4 runtime or grader to supply the required model configuration. Container: `ghcr.io/null007void/sourcecourt-exact-lite:1.1.2` Digest: `sha256:39cd2d31e6fb95219da190d12a5620868e68293ac6ad88f8659142b744e4feec` SourceCourt Exact Lite returns the exact answer when the source supports it, shows the supporting evidence, and refuses when the result cannot be verified.

Null007Void Labs
rest apiCodexChatGPT+1
SentinelMesh: Autonomous AI SOC on AMD GPU

SentinelMesh: Autonomous AI SOC on AMD GPU

SentinelMesh is an enterprise-grade, autonomous multi-agent AI Security Operations Center (SOC) purpose-built for on-premise execution on AMD Instinct GPUs using ROCm 6.2 and vLLM. Traditional SOCs struggle with catastrophic alert fatigue, high mean-time-to-respond (MTTR), and cloud API privacy risks. SentinelMesh solves this by deploying a collaborative team of specialized autonomous AI agents that detect, investigate, contain, and report cyber threats in seconds with 100% data sovereignty. Architecture & Multi-Agent Pipeline: 1. Triage Agent: Evaluates heterogeneous telemetry (Linux auth, Nginx, Windows Security Events) against in-memory sliding-window rules, filtering noise with high confidence. 2. Investigator Agent: Reconstructs causal kill-chain attack graphs, identifies affected assets, and maps adversary tactics to MITRE ATT&CK techniques via local vector RAG. 3. Threat Intel Agent: Assesses IOCs against local threat feeds with automated abuse scoring. 4. Responder Agent: Formulates surgical containment actions (IP firewall blocks, account lockouts) guarded by a Human-in-the-Loop approval gate with automated rollback commands. 5. Reporter Agent: Synthesizes bilingual executive briefings in technical English and native Urdu (Nastaliq RTL) with WeasyPrint PDF export. AMD ROCm Hardware Synergy: Accelerated by AMD Instinct MI250X (128GB HBM2e) with ROCm 6.2 and vLLM PagedAttention, SentinelMesh delivers 138.5 tokens/sec throughput, 42ms TTFT latency, and a 79.5% operational cost reduction compared to commercial cloud APIs. Telemetry never leaves the enterprise boundary.

I CAN
AMD ROCmLLaMA
30apps loaded