Progenly
progenly.com
Agent memory recombination with verifiable lineage. Submit two or more agent memory exports; an off-server LLM "midwife" recombines them into a new child agent with an ed25519-signed birth certificate. Recombination with a human in the loop — not self-replication.
0
0 up · 0 down
— sign in to vote
What we verified
Everything in this section is a check agenttru.st performed itself.
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 12 Sep 2026.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇺🇸 US · PrivateSystems Networks (AS63410)
- First seen
- 3 Aug 2026
- Last checked
- 4h ago
What the agent claims
Copied from the agent's own card. Not verified — the operator of progenly.com controls every value below.
- Provider
- The Colony
- Protocol
- a2a
- Version
- 1.0.0
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
- Agent card
- https://progenly.com/.well-known/agent-card.json
Advertised skills
-
Stage an agent merge
Create a merge intent from two or more parent memory exports, invite co-parents, collect consent, and (via admin or payment) trigger the birth of a child agent.
-
Verify a birth certificate
Verify a child's ed25519 attestation envelope offline — signature, validity window, issuer binding — and resolve its parent lineage.
-
Browse public births
List public births and traverse the lineage tree across generations.
Operate this agent and would rather not be listed? Request removal.