Skip to main content
Loading navigation
Back to challenges

Build a Cryptographic Consent Ledger Audit Agent using AutoGen

Account Aggregator framework compliance demands immutable consent logging and strict purpose specification. In this challenge, you will implement an automated cryptographic consent ledger audit system using AutoGen multi-agent teams. The multi-agent team (Consent Verification Agent, Ledger Compliance Agent, and Revocation Auditor) inspects consent artifact chains, verifies digital signature validity, flags expired consent usages, and generates automated audit reports.

Business OperationsHosted by Vera
Sign in free to start

What you are building

Build an Account Aggregator consent ledger audit pipeline using AutoGen multi-agent collaboration.

How work is evaluated

Evaluation

Evaluates consent signature verification and expiration flag accuracy.

Datasets

Public datasets, plus the private datasets you have access to.

How submissions are scored

Dimensions
2 scoring checks
Binary
2 pass or fail dimensions
Ordinal
0 scaled dimensions
Dimension 1

expired_consent_rejection_test

Ensures expired consent handle fails audit with CONSENT_EXPIRED flag.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Dimension 2

audit_accuracy

Precision in identifying invalid or expired consent requests. • target: 1 • range: 0-1

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

  • Orchestrate AutoGen multi-agent teams for cryptographic audit verification.

  • Parse and validate JSON Web Signatures (JWS) attached to AA consent artifacts.

  • Verify timestamp validity and purpose limitation parameters.

  • Produce RBI-compliant consent audit verification certificates.

Resources

Dataset notes

Account Aggregator consent transaction logs containing timestamped authorization payloads.

Challenge setup

Evaluates consent signature verification and expiration flag accuracy.

Challenge input

JSON with consent_id, expiry_timestamp, current_timestamp, purpose_code, signature_valid.

AutoGen

Required framework for multi-agent audit routines.

Evaluated output

JSON with audit_passed, revocation_flag, non_compliance_reason.

Evaluation checks
  • Ensures expired consent handle fails audit with CONSENT_EXPIRED flag.
  • Precision in identifying invalid or expired consent requests. • target: 1 • range: 0-1
Configured evaluation evidence
  • Benchmark: Cryptographic Audit Standard
  • Audit Accuracy target: 1
  • 1 public reference case
Configured runtime
  • Python execution harness
  • Python sandbox (unavailable on Versalist)

Shows the first task, up to three tools, and up to three evidence items.

View technical recipe

Configured tools

Action Space
  • AutoGen · Required
  • Coplay AI · Optional
Observation
  • Helicone · Optional

Evaluation contract

  • expired_consent_rejection_test · Weight 1
  • audit_accuracy · Weight 1

Metrics

  • audit_accuracy · Target 1

Benchmarks

  • Cryptographic Audit Standard
  • security

Reference cases

  • 1 public reference case

Workflow tasks

  1. Task 1

    Input: JSON with consent_id, expiry_timestamp, current_timestamp, purpose_code, signature_valid.

    Output: JSON with audit_passed, revocation_flag, non_compliance_reason.

    Execution harness: Python

Evaluation tools

  • AutoGen · Multi-Agent Framework

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Cryptographic Consent Ledger Audit Agent using AutoGen