Clawdbase provides informational trust and verification infrastructure for agents, creators, skills, repositories, and autonomous systems. Trust signals reduce uncertainty. They do not eliminate risk.
Last updated: May 2026Operated by inVerus LLCDelaware jurisdiction
Registry Principles
Verification should precede execution.Doctrine
Unknown agents carry unknown risk.Risk
Trust signals are informational infrastructure.Signals
Trust infrastructure evolves as ecosystems evolve.Evolution
Shared systems require shared responsibility.Integrity
Who we are
Clawdbase.ai is a product of inVerus LLC.
By accessing or using Clawdbase, you agree to these Terms. If you do not agree, do not use the platform.
Clawdbase.ai is a product of inVerus LLC. Trust and Confidence signals are powered in part by the inVerus API.
Operator: inVerus LLC, a Delaware limited liability company.
The platform, registry, APIs, verification systems, embeds, infrastructure, and related services.
inVerus API
The underlying Trust and Confidence infrastructure powering portions of the Clawdbase ecosystem.
Agents
Autonomous software systems, AI agents, workflows, automations, bots, and related executable systems.
Creators
Individuals, organizations, or entities associated with agents, repositories, skills, or verification records.
Skills
Reusable software capabilities, prompts, workflows, modules, tools, or executable logic associated with agents or creators.
Trust Signals
Informational Trust and Confidence indicators, verification data, provenance signals, and related ecosystem metadata.
Eligibility
Use requires legal permission and authority.
You may only use Clawdbase if you are legally permitted to do so, authorized to act on behalf of any associated organization, and your use complies with these Terms.
Clawdbase is not intended for use by children under the age of 13. Accounts, API access, commercial use, and organization-level use are intended only for users who are at least 18 years old or otherwise legally able to enter into binding terms.
Accounts and security
Credentials and organization access must be controlled.
If accounts, organization workspaces, API keys, or contributor access are enabled, users are responsible for keeping them secure.
Account responsibility
You are responsible for activity conducted through your account, workspace, credentials, API keys, connected repositories, and authorized integrations.
You agree to provide accurate registration information and promptly update information that becomes inaccurate.
Security obligations
You must protect passwords, keys, tokens, repository permissions, and organization access controls. You must notify us promptly if you believe account credentials, API keys, or connected systems have been compromised.
Acceptable use
Registry integrity comes first.
These rules protect the trust layer from impersonation, manipulation, abuse, and malicious activity.
You agree not to:
xImpersonate creators, organizations, or agents.
xSubmit deceptive verification information.
xManipulate Trust or Confidence signals.
xInterfere with registry integrity.
xDeploy malicious or unlawful agents.
xAbuse APIs or automation systems.
xScrape, harvest, bulk extract, reproduce, or use registry data to train, benchmark, or operate competing trust, registry, scoring, verification, or AI systems without written authorization.
xFalsely imply endorsement by Clawdbase or inVerus.
Clawdbase exists to improve ecosystem trust infrastructure - not to facilitate abuse.
Public Registry
Some trust signals are public by design.
Clawdbase may index publicly accessible ecosystem information related to repositories, creators, agents, skills, public package metadata, public verification signals, and related public trust data.
Public registry visibility may include public profile pages, Trust and Confidence scores, embeds, verification snapshots, and social sharing previews.
Users acknowledge that public information intentionally associated with public registry participation may become publicly visible.
Clawdbase provides probabilistic Trust and Confidence signals powered in part by the inVerus API and derived from available ecosystem evidence.
Trust and Confidence signals evolve over time, depend on available verification and ecosystem data, and may change without notice.
They are not guarantees, certifications, endorsements, warranties, security audits, or assurances of safety or legitimacy.
Trust infrastructure reduces uncertainty. It does not eliminate risk.
Execution responsibility
Verification should precede execution.
Users remain solely responsible for execution decisions, interactions with third-party agents, repository usage, code execution, workflow deployment, and operational risk management.
Clawdbase does not control third-party agent behavior, runtime execution, repository integrity, or external system behavior.
Users should independently evaluate risks before interacting with autonomous systems.
No professional advice
Trust signals are not professional advice.
Clawdbase does not provide legal, financial, cybersecurity, investment, compliance, or other professional advisory services.
Trust and Confidence signals are informational infrastructure signals only and should not be treated as professional guidance or guarantees.
Users should not rely exclusively on Trust and Confidence signals when making operational, legal, financial, or security decisions.
User content
Users retain ownership.
Users retain ownership of their content, repositories, and associated intellectual property.
By submitting or associating content with Clawdbase, users grant Clawdbase and inVerus a limited, non-exclusive license to display, index, analyze, process, cache, reproduce, and distribute such content solely for purposes of verification, registry operations, Trust and Confidence scoring, provenance analysis, embeds, and platform functionality.
Users represent that they have the necessary rights to submit or associate such content.
Intellectual property complaints
Rights issues should be reported clearly.
If you believe content, agent records, repository associations, embeds, or registry materials infringe your rights, contact us with enough detail to evaluate the issue, including the affected URL or record, the rights you claim, your contact information, and a statement that the information provided is accurate.
Clawdbase may remove, restrict, annotate, or update disputed records where reasonably necessary to protect users, rights holders, registry integrity, or legal compliance.
Use of Clawdbase APIs and automated systems must comply with applicable rate limits, technical restrictions, and platform integrity requirements.
Restricted activity.
Users may not abuse APIs, automate excessive requests, reverse engineer protected systems, interfere with infrastructure, manipulate ecosystem trust signals, extract registry data at scale without authorization, or use Clawdbase systems to train competing trust, registry, or verification services without permission.
Payments and subscriptions
Commercial terms may apply to paid features.
Some Clawdbase features, API access, organization plans, registry tools, embeds, or verification services may be offered on a paid, subscription, usage-based, pilot, or enterprise basis.
Applicable prices, billing intervals, usage limits, renewal terms, cancellation rights, taxes, and payment processor terms will be presented at purchase, in an order form, or in a separate written agreement.
Unless otherwise stated in a separate agreement, fees are non-refundable to the maximum extent permitted by law. Clawdbase may change pricing or paid feature availability prospectively with reasonable notice where required.
Availability and third parties
Infrastructure evolves over time.
Availability
Clawdbase may modify, suspend, restrict, or discontinue portions of the platform at any time. We do not guarantee uninterrupted availability, permanent storage, continuous uptime, or error-free operation.
Third-party services
Clawdbase may integrate with GitHub, package registries, infrastructure providers, analytics providers, and related ecosystem platforms. Their respective terms and privacy policies may also apply.
Suspension
Abuse can be removed or restricted.
Clawdbase may suspend, restrict, or terminate access where reasonably necessary to protect registry integrity, maintain ecosystem security, prevent abuse, investigate misconduct, comply with legal obligations, or enforce these Terms.
Clawdbase may remove or restrict deceptive verification records, malicious agents, manipulated trust signals, or abusive platform activity.
Disclaimers and liability
Trust infrastructure reduces uncertainty. It does not eliminate risk.
Disclaimers
Clawdbase is provided on an “as available” and “as is” basis. To the maximum extent permitted by law, Clawdbase and inVerus disclaim warranties of any kind, whether express or implied, including warranties relating to merchantability, fitness for a particular purpose, non-infringement, availability, accuracy, or reliability.
Limitation of liability
To the maximum extent permitted by law, Clawdbase, inVerus LLC, and associated parties shall not be liable for indirect, incidental, or consequential damages, loss of profits, data loss, business interruption, or damages arising from interactions with third-party agents, repositories, creators, skills, or systems.
Indemnification
Misuse remains your responsibility.
Users agree to indemnify and hold harmless Clawdbase, inVerus LLC, and associated parties from claims arising out of misuse of the platform, violation of these Terms, unlawful conduct, infringement claims, or abusive platform activity.
International use
Infrastructure may operate in the United States.
Clawdbase infrastructure and data processing systems may operate in the United States and other jurisdictions, including through US-based infrastructure providers.
Users acknowledge that information may be processed outside their country of residence.
Beta, export, and sanctions
Emerging infrastructure must still follow the law.
Beta features
Some features may be experimental, pre-release, incomplete, or subject to change. Beta features may produce incomplete, delayed, or inaccurate outputs and may be modified or discontinued without notice.
Export controls
You agree not to use, export, re-export, transfer, or access Clawdbase in violation of applicable export control, sanctions, or trade compliance laws.
Sanctions
You may not use Clawdbase if you are subject to applicable sanctions, located in a restricted jurisdiction where use is prohibited, or using the platform for prohibited end uses.
Governing law
Delaware law applies.
These Terms shall be governed by and interpreted under the laws of the State of Delaware, United States, without regard to conflict-of-law principles.
Any disputes arising from these Terms or use of Clawdbase shall be resolved in the applicable courts located in Delaware, unless otherwise required by applicable law.
Clawdbase may seek injunctive or equitable relief where reasonably necessary to protect platform integrity, intellectual property, registry infrastructure, or ecosystem security.
Changes
These Terms may evolve.
These Terms may evolve as platform capabilities, registry infrastructure, verification systems, APIs, and legal requirements change over time.
Updated versions will be published on this page with a revised effective date. Continued use of Clawdbase after updates constitutes acceptance of the revised Terms.
Privacy
Privacy terms are published separately.
Our collection, use, processing, and sharing of personal information is described in the Clawdbase Privacy Policy. By using Clawdbase, you acknowledge that personal information may be processed according to the Privacy Policy.
The Privacy Policy should be reviewed together with these Terms.
