Agent Service

Note

This analysis is based solely on the self-reported project description provided by the caller. No external verification, revenue data, traction metrics, or third-party sources are available. All claims are treated as stated by the author and not proven.

The description states that Agent Service is an AI-operated digital sovereignty platform. It allows owners to register digital assets and define authorized uses, restrictions, limits, and exceptions in natural language.

• GPT-5.6 compiles this intent into an immutable policy proposal.
• A human must review and approve the exact immutable version before activation.
• The system supports:
  • Protected asset custody
  • ECDSA P-256 and ML-DSA-65 signature verification
  • Preventive readiness assessment
  • Signed canary preparation
  • Deterministic policy enforcement
  • Hybrid cryptographic operation
  • Organization-scoped operational records
  • Human Control Plane for approvals and system oversight

The platform is implemented as four connected services:

• A Next.js web application
• A Fastify gateway
• A background worker
• A managed PostgreSQL database

It uses TypeScript, Node.js, Docker, Vitest, Playwright, GitHub, Railway, classical cryptography, and post-quantum cryptographic components.

Inference The system is built to support both AI-assisted policy creation and human oversight, with a focus on security and verifiability. However, no evidence of actual deployment or usage beyond the demo exists.

The author positions Agent Service as an AI-operated digital sovereignty platform that connects owner intent with preventive security, cryptographic custody, and deterministic enforcement.

• It is described as not merely storing assets or generating policy text, but integrating intent translation, approval workflows, and verifiable records.
• The tagline emphasizes protection of digital assets, enforcement of owner-defined policies, tracing access, and post-quantum readiness.
• The author claims the system preserves human authority: GPT-5.6 proposes and explains; the owner decides.

Claim

The platform aims to make digital sovereignty practical through AI assistance, cryptographic verification, and always-subject-to-human-control design.

Inference The positioning reflects a niche in cybersecurity and digital asset governance where AI is used for policy generation but not decision-making. This suggests a focus on compliance, risk control, or enterprise security use cases.

The description does not name specific customers or target industries. However, it implies a focus on:

• Owners of digital assets who want to define and enforce access policies
• Organizations seeking secure, auditable, and AI-assisted policy management
• Users concerned with digital sovereignty and control over their data

Inference The ICP likely includes enterprise security teams, compliance officers, or developers managing sensitive digital resources in regulated environments.

Not evidenced No explicit customer segments, personas, or use cases beyond the author’s own demonstration are provided.

There is no evidence of a business model or pricing structure in the description.

Not evidenced No mention of monetization strategy, subscription tiers, licensing, or revenue streams.

The system is built using:

• GPT-5.6 for policy compilation
• Codex for engineering assistance
• Next.js, Fastify, Node.js, TypeScript
• Docker, Railway, PostgreSQL
• Classical and post-quantum cryptography (ECDSA P-256, ML-DSA-65)
• Vitest, Playwright for testing
• GitHub for version control

The architecture consists of four services:

1. Next.js web application
2. Fastify gateway
3. Background worker
4. PostgreSQL database

Inference The platform is designed with modern cloud-native and security practices in mind, including containerization, cryptographic integrity, and human-in-the-loop controls.

The project was submitted as a hackathon entry (Build Week) and includes:

• A deployed release candidate across four Railway services
• A synthetic, non-sensitive evaluation asset used for demonstration
• Functional policy compilation with GPT-5.6
• Zero blocking ambiguities and conflicts in the final compiled policy
• 100/100 preventive readiness score

Not evidenced No real-world deployment, customer feedback, or adoption data beyond the author’s own account.

The description does not mention competitors or direct market positioning. However, it implies a role in:

• Digital asset governance
• AI-assisted policy enforcement
• Cryptographic custody and access control
• Post-quantum security

Inference The platform may compete with or complement solutions in the cybersecurity, compliance, and digital sovereignty spaces, particularly those involving AI-driven access control.

Not evidenced No competitive landscape, market size, or differentiation from existing tools is provided.

• Unproven traction: The system has only been demonstrated in a hackathon setting with synthetic data.
• Single-founder model: Only one team member (Leonardo Martínez) is listed.
• AI dependency: Heavy reliance on GPT-5.6 for policy compilation raises concerns about scalability, consistency, and control.
• Limited evidence of real-world application: No customers, users, or feedback beyond the author’s own account.
• No pricing or monetization strategy: Unclear how the platform will generate revenue.

Inference The project is in early development and lacks commercial validation or market traction. It may be a proof-of-concept rather than a scalable product.

1. What specific use cases are you targeting, and how do they align with current market needs?
2. How do you plan to scale beyond the current hackathon prototype?
3. Are there any real-world partners or early adopters involved in testing or validating this platform?
4. What is your roadmap for monetization and go-to-market strategy?
5. How do you handle edge cases where GPT-5.6 fails to interpret intent accurately?
6. What are the key assumptions about user behavior and adoption that underpin your design choices?