aicryptogroup

videberta v3 base

Search / embeddings

This receipt records checks for this exact file; it does not prove safety or that it will run on your device. Read the receipt

Model details
text embeddingsLicense: apache-2.0SHA-256 recorded for 7 of 9 filessafetensors · BIN
Quick answer: compatibility and sources

Can I run videberta-v3-base on my computer?

It depends on your memory, processor, file format and runtime. A download is not confirmed by the current file evidence; inspect the file record before trying it. A file-size fit is an estimate, not a successful run or speed promise. Read the license before use.

videberta-v3-base is an embedding model for text embeddings. Model weights are learned parameters; a runtime loads them. A hosted file is an individual file Hugging Bay can serve. SHA-256 identifies exact file bytes. The availability date above applies to this file record, not the upstream metadata update date.

As of the recorded file availability check on .

Recorded SHA-256 for model.safetensors: 81909095c8e090310052d14da5bbf68ca085a5774fbcdb2ccf46f6e05f3b1f3e. Exact file evidence · Machine-readable source facts · Run evidence and any recorded receipts. A checksum fingerprints only the named file bytes; it does not prove safety, quality, a complete multi-file selection or a successful run.

Updated · Page-copy source revision 8871bab84e1cf80aea1686a944ec335078a6c036 · Source files: apps/web/lib/model-page-template.mjs, apps/web/lib/model-page-v3.mjs, apps/web/lib/aeo-page.mjs · Full revision record

Model metadata: As of at the model source. Popularity counters are source-reported, not measured by Hugging Bay. Availability checked .

Key facts

Catalog record
Summarizes upstream metadata; it is not itself a download or run receipt.
File evidence
Lists exact filenames, availability and any recorded SHA-256 for individual files.
Run evidence
Reports measured results only when a receipt exists for named file bytes and a setup; otherwise unmeasured.
Checksum scope
SHA-256 fingerprints one file’s bytes; it does not prove safety, quality or a multi-file bundle.

Evidence you can inspect (plain text)

  • This page’s quick answer names the file record for hf-model-aicryptogroup-videberta-v3-base.
  • Open /artifact/hf-model-aicryptogroup-videberta-v3-base/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-aicryptogroup-videberta-v3-base for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-aicryptogroup-videberta-v3-base/card.md for machine-readable source facts (not a runtime test).
  • A matching checksum on this page fingerprints only the named bytes shown in file evidence.

Unmeasured states are stated explicitly; this page does not invent run scores or compatibility guarantees.

Which date applies to which fact

  • File availability check:
  • Committed page-copy sources:
  • Upstream model metadata: Dates on artifact records when shown; not implied by page-copy revision
  • Run receipts: Only on /evidence pages when recorded; otherwise unmeasured

Page-copy revision (Updated line above) identifies committed text sources, not upstream model edits or test outcomes.

Requirements and source record
aicryptogroup/videberta-v3-base

Content controls: not assessed.

The catalog lists this model for finding useful details in data. Catalog sources: license, cardMetadata.license, task, cardMetadata.pipelineTag.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileGrößeSHA-256QuelleHerunterladen
Weights
model.safetensors461.6 MB
81909095…5f3b1f3e81909095c8e090310052d14da5bbf68ca085a5774fbcdb2ccf46f6e05f3b1f3e
Download availability is being checked.File metadata
pytorch_model.bin461.7 MB
b43597c4…11d76159b43597c49df7afbcd452cb9a7b8a6e6b6a1262e7cafcc49adbaa6b7511d76159
Download availability is being checked.File metadata
Tokenizer & config
added_tokens.json17 bytes
2937a2ef…1ecfa2b22937a2efccc6ec5e1b2398116d6505474fc3028bdfbcffb8201491401ecfa2b2
Download availability is being checked.File metadata
config.json865 bytes
79f4cb32…89e19efc79f4cb32349df1fafca0536e1a4566936c2e82c073b44f6eea6de02c89e19efc
Download availability is being checked.File metadata
special_tokens_map.json156 bytes
fcfbeb4e…24d827dafcfbeb4e25cd37fb5b8030406394253b245230fd3b552750092bab7d24d827da
Download availability is being checked.File metadata
spm.model873.4 KB
1ccc487b…bb608a731ccc487b95cd81f49654146df33a9e4db612d52da52606fa6064ba15bb608a73
Download availability is being checked.File metadata
tokenizer_config.json269 bytes
44c6340d…0889f8a744c6340d9cf0a73643a86b936f6edef075050f0b35f73175429fdf3b0889f8a7
Download availability is being checked.File metadata
Docs
.gitattributes1.39 KB—Download availability is being checked.File metadata
README.md28 bytes—Download availability is being checked.File metadata

Einen Download prüfen

In the folder where you saved added_tokens.json, run:

macOS
shasum -a 256 -- 'added_tokens.json'
Linux
sha256sum -- 'added_tokens.json'
Windows
Get-FileHash -LiteralPath 'added_tokens.json' -Algorithm SHA256

Compare the result with the recorded SHA-256.