feat(ecosystem): Add QuantumShield API to Services/Endpoints #891
+15
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added metadata for QuantumShield API including name, category, logo URL, description, and website URL.
🟡 Heimdall Review Status
|
|
@mbennett-labs is attempting to deploy a commit to the Coinbase Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adding QuantumShield API to the x402 ecosystem under Services/Endpoints.
About QuantumShield API
Security-as-a-service API for token risk analysis powered by x402 micropayments on Base. Provides comprehensive token security scores, honeypot detection, and holder risk analysis.
Changes
typescript/site/app/ecosystem/partners-data/quantumshield-api/metadata.jsontypescript/site/public/logos/quantumshield-api.png<!--Thanks for contributing to x402!
Please fill out the information below to help reviewers understand your changes.
Note: We require commit signing.
See here for instructions: https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification
-->
Description
Tests
Checklist
- I have formatted and linted my code
- All new and existing tests pass
- My commits are signed (required for merge) -- you may need to rebase if you initially pushed unsigned commits
go vet ./...` from the `/go` directory-->