feat(payments): add Pay for Data (Heurist) use case

[joshuamarksmith]

A Strands-based finance research agent that calls paid Heurist x402 endpoints for real-time prices, SEC filings, and macro indicators. The AgentCorePaymentsPlugin intercepts HTTP 402 responses, asks the AgentCore payment manager to generate a payment proof against the configured payment instrument and payment session, and retries automatically — tool code stays an ordinary http_request call. Data is analyzed in AgentCore Code Interpreter and exported as charts and reports.

Highlights:

• HTTP 402 payment processing via AgentCorePaymentsPlugin — no manual payment code in tools
• Embedded wallet (Coinbase CDP) with USDC as the settlement asset
• AgentCore Code Interpreter for pandas/matplotlib analysis and artifact export
• Public PyPI dependencies only (bedrock-agentcore==1.9.0) — no bundled or file-based SDK components
• Targets x402 on Base mainnet (Heurist endpoints settle on Base)

Adds:

• 01-tutorials/13-AgentCore-payments/02-use-cases/pay-for-data/
  • pay-for-data.ipynb (notebook walkthrough)
  • heurist_finance_agent/ (agent, catalog, config, artifact_export)
  • scripts/ (sync_registry, run CLI entry points)
  • requirements.txt, .env.example, README.md, .gitignore

Updates:

• 01-tutorials/13-AgentCore-payments/README.md: add Use Cases table entry
• 01-tutorials/13-AgentCore-payments/02-use-cases/README.md: add use case overview and highlights

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[github-actions]

Latest scan for commit: 2391da9 | Updated: 2026-05-12 10:00:17 UTC

Security Scan Results

Scan Metadata

• Project: ASH
• Scan executed: 2026-05-12T09:59:56+00:00
• ASH version: 3.0.0

Summary

Scanner Results

The table below shows findings by scanner, with status based on severity thresholds and dependencies:

Column Explanations:

Severity Levels (S/C/H/M/L/I):

• Suppressed (S): Security findings that have been explicitly suppressed/ignored and don't affect the scanner's pass/fail status
• Critical (C): The most severe security vulnerabilities requiring immediate remediation (e.g., SQL injection, remote code execution)
• High (H): Serious security vulnerabilities that should be addressed promptly (e.g., authentication bypasses, privilege escalation)
• Medium (M): Moderate security risks that should be addressed in normal development cycles (e.g., weak encryption, input validation issues)
• Low (L): Minor security concerns with limited impact (e.g., information disclosure, weak recommendations)
• Info (I): Informational findings for awareness with minimal security risk (e.g., code quality suggestions, best practice recommendations)

Other Columns:

• Time: Duration taken by each scanner to complete its analysis
• Action: Total number of actionable findings at or above the configured severity threshold that require attention

Scanner Results:

• PASSED: Scanner found no security issues at or above the configured severity threshold - code is clean for this scanner
• FAILED: Scanner found security vulnerabilities at or above the threshold that require attention and remediation
• MISSING: Scanner could not run because required dependencies/tools are not installed or available
• SKIPPED: Scanner was intentionally disabled or excluded from this scan
• ERROR: Scanner encountered an execution error and could not complete successfully

Severity Thresholds (Thresh Column):

• CRITICAL: Only Critical severity findings cause scanner to fail
• HIGH: High and Critical severity findings cause scanner to fail
• MEDIUM (MED): Medium, High, and Critical severity findings cause scanner to fail
• LOW: Low, Medium, High, and Critical severity findings cause scanner to fail
• ALL: Any finding of any severity level causes scanner to fail

Threshold Source: Values in parentheses indicate where the threshold is configured:

• (g) = global: Set in the global_settings section of ASH configuration
• (c) = config: Set in the individual scanner configuration section
• (s) = scanner: Default threshold built into the scanner itself

Statistics calculation:

• All statistics are calculated from the final aggregated SARIF report
• Suppressed findings are counted separately and do not contribute to actionable findings
• Scanner status is determined by comparing actionable findings to the threshold

Scanner	S	C	H	M	L	I	Time	Action	Result	Thresh
bandit	0	0	0	0	0	0	811ms	0	PASSED	MED (g)
cdk-nag	0	0	0	0	0	0	28.3s	0	PASSED	MED (g)
cfn-nag	0	0	0	0	0	0	10ms	0	PASSED	MED (g)
checkov	0	0	0	0	0	0	4.6s	0	PASSED	MED (g)
detect-secrets	0	0	0	0	0	0	777ms	0	PASSED	MED (g)
grype	0	0	0	0	0	0	41.6s	0	PASSED	MED (g)
npm-audit	0	0	0	0	0	0	169ms	0	PASSED	MED (g)
opengrep	0	0	0	0	0	0	<1ms	0	SKIPPED	MED (g)
semgrep	0	0	0	0	0	0	<1ms	0	MISSING	MED (g)
syft	0	0	0	0	0	0	2.1s	0	PASSED	MED (g)

[mvangara10]

Please update the use case to use AgentCore runtime and AgentCore observability

[leewc]

Changes LGTM from my side. You might want to address Madhu's comments