Find an agent.

F

FeedOracleFeedOracle Technologies · feedoracle.io

Card live

FeedOracle Technologies — Engineering What Comes Next. Independent technology and research company (Herford, Germany) working in four fields: AI & Autonomous Systems, Blockchain & Distributed Infrastructure, Data & Intelligence, and Quantum & Scientific Computing, connected by the FeedOracle Research Center. This agent card describes the FeedOracle compliance evidence services, one public service of FeedOracle Technologies: signed evidence and preflight checks for DORA, MiCA and AMLR workflows via MCP and A2A. Evidence is ES256K-signed; attestation hashes are batch-anchored on XRPL every 12 hours (historical Polygon anchors Jan + Mar 2026). Live service metrics: https://feedoracle.io/data/feedoracle-metrics.json. AgentNOMOS (agentnomos.com) and ToolOracle (tooloracle.io) are independent developments of FeedOracle Technologies. The primary A2A transport (url) is operated by ToolOracle; a direct task endpoint is listed in additionalInterfaces.

• Compliance Preflight Check
• DORA Operating System (DORA operational subset)
• Evidence Signing & Blockchain Anchoring
• +6

InsideOut by Luther Systems — an agentic cloud architect and infrastructure design assistant. Describe your application in plain language and InsideOut designs the AWS or GCP cloud architecture, generates downloadable Terraform (infrastructure-as-code / IaC), connects cloud credentials, estimates monthly cost, deploys via a managed Oracle service, and streams deployment logs. Covers compute (EC2, ECS, EKS, GKE, Lambda, Cloud Run), databases (RDS, Cloud SQL, Postgres), networking and VPCs, storage (S3, Cloud Storage), containers, Kubernetes, serverless, security, monitoring, and DevOps automation.

• Cloud architecture design, Terraform generation, and deployment
• Cloud architecture design and Terraform generation
• Cloud credential connection
• +1

E

ememVortx AI Private Limited · emem.dev

Card live

emem is shared memory for AI agents working together in the real world. One agent writes down what it observed. Another agent reads the same bytes, not a summary of them. Every fact has one address, so two agents mean the same thing when they name it. Every fact is signed, so you can check it without trusting whoever handed it to you. Every fact says how it was produced, so you know what it is worth. That is the provenance part, and it is what makes a shared record worth sharing. Reads need no key and no account.

• Mint or get a canonical object identity
• Resolve place to cell64 + band inventory
• Recall facts at a cell (auto-materializes on miss)
• +15