Frequently Asked Questions

Common questions about attest.ink and how it works

How does attest.ink work offline?

attest.ink operates primarily as a client-side application, which means:

  • Embed Badge: This option generates self-contained HTML with full attestation data embedded directly in the code. These badges work completely offline and can be shared anywhere without requiring internet access.
  • Local Storage: When you create an attestation, it's stored in your browser's localStorage. This allows you to verify attestations you've created on the same device/browser without internet.
  • No Server Dependency: The core verification process happens entirely in your browser using JavaScript cryptography libraries.

What are permanent short URLs?

Permanent short URLs (like https://attest.ink/s/abc123) are a premium feature that:

  • Never expire - your attestations are stored permanently
  • Work across all devices and browsers
  • Cost $20 for lifetime access (unlimited URLs)
  • Include API access for programmatic creation

Free alternatives for sharing:

  1. Use the "Embed Badge" option (includes full attestation data)
  2. Use the full data URL (works anywhere but is very long)
  3. Save and share the attestation JSON file

What's the difference between badge options?

  • Embed Badge: Self-contained HTML with full attestation data embedded. Works offline, perfect for sharing.
  • Direct Link: A short URL that requires the attestation to be in localStorage or on the server.
  • Data URL: A long URL containing the entire attestation encoded in base64.
  • LaTeX Badge: Special formatting for academic papers with footnotes.
  • Markdown Badge: For README files and documentation.

Can I verify attestations from other browsers/devices?

Yes, but you need to use one of these methods:

  • Use an embed badge (contains all data)
  • Use a data URL (contains all data)
  • Share the attestation JSON file
  • Pay for and use short links

How do I use LaTeX badges in academic papers?

LaTeX badges are designed for academic citations:

  1. Create your attestation with the content
  2. Select "LaTeX" as the badge style
  3. Copy the generated LaTeX code
  4. Paste it into your paper where you want the badge
  5. The badge includes a footnote with the verification URL

Best practice for LaTeX papers: To avoid hash validation issues when including attestation URLs in your paper:

  1. Create a separate file called ai-attestation.tex
  2. Put your attestation badge and URL in this separate file
  3. Include this file in your main paper using \input{ai-attestation}
  4. Generate the attestation for your main content (excluding the ai-attestation.tex file)

This approach keeps the attestation URL separate from the content being attested, avoiding circular dependency issues.

Is my data private?

Yes, attest.ink prioritizes privacy:

  • All attestation creation happens in your browser
  • No data is sent to servers during creation
  • You can keep prompts private (only the hash is included)
  • localStorage data stays on your device
  • You control what data to share via badges/links
  • No analytics or tracking scripts
  • Open source code you can audit

How does payment processing work?

Payments are processed securely through Stripe:

  • One-time payment of $20 for lifetime access
  • Only email and ZIP code required (for tax calculation)
  • California residents pay sales tax automatically
  • Professional email receipt with API key
  • Billing appears as "McBooBoo LLC" on statements
  • Immediate access after payment

How do I use the API?

With a premium API key, you can create attestations programmatically:

# Create attestation
curl "https://attest.ink/api/create.html?content_name=My%20Project&model=gpt-4"

# Create short URL (requires API key)
curl -X POST https://attest.ink/api/shorten \
  -H "Content-Type: application/json" \
  -d '{"dataUrl": "...", "apiKey": "ak_..."}'

See the API documentation for complete details.

What's the difference between AI roles?

  • AI Generated: Content created entirely by AI (100% AI)
  • AI Assisted: Human and AI collaboration
  • AI Edited: Human-created content refined by AI

Which AI models are supported?

Over 100 AI models from major providers including:

  • OpenAI: GPT-5 (coming soon), GPT-4, GPT-3.5, DALL-E
  • Anthropic: Claude 4.1 Opus, Claude 3.5 Sonnet, Claude 3 series
  • Google: Gemini 1.5 Pro, Gemini Ultra, PaLM 2
  • Meta: Llama 3 70B, Code Llama
  • Plus many more... Stability AI, Midjourney, Mistral, Cohere, xAI

The list is regularly updated as new models are released.

Can I automate attestations in CI/CD?

Yes! attest.ink is designed for automation:

# GitHub Actions example
- name: Create AI Attestation
  run: |
    ATTESTATION=$(curl -s "https://attest.ink/api/create.html?content_name=README&model=github-copilot")
    echo "$ATTESTATION" > attestation.json

See the CI/CD guide for platform-specific examples.