Skip to content

feat: multi-chain API response support (v1.3.0)#4

Merged
vvillait88 merged 3 commits intomainfrom
feat/multi-chain-response
Mar 31, 2026
Merged

feat: multi-chain API response support (v1.3.0)#4
vvillait88 merged 3 commits intomainfrom
feat/multi-chain-response

Conversation

@vvillait88
Copy link
Copy Markdown
Contributor

Summary

  • subject.chain (string) → subject.chains (string[])
  • Per-chain data in chains[] array (score with confidence/dimensions, classification, identity, activity, evidence)
  • Top-level score is operator-level (no confidence/dimensions)
  • No top-level classification (per-chain only in chains[])
  • Assess response includes operator_score, reputation, agents
  • Version bump to 1.3.0
  • Updated deps

Test plan

  • CI passes

🤖 Generated with Claude Code

vvillait88 and others added 3 commits March 30, 2026 23:08
- subject.chain (string) → subject.chains (string[])
- Per-chain data in chains[] array (score, classification, identity, activity, evidence)
- Top-level score is operator-level (no confidence/dimensions)
- No top-level classification (per-chain only)
- Assess includes operator_score, reputation, agents
- Version bump to 1.3.0

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Verifies response shapes match types against live dev API.
Covers: subject.chains, top-level score (no confidence/dimensions),
per-chain score/classification/identity/activity/evidence, chain filter,
operator_score, reputation, assess decision, policy deny.
Skips when AGENTSCORE_API_KEY is not set.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vvillait88 vvillait88 merged commit cb9424a into main Mar 31, 2026
6 checks passed
@vvillait88 vvillait88 deleted the feat/multi-chain-response branch March 31, 2026 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant