Learn how to interact with this file using the Ouro SDK or REST API.
API access requires an API key. Create one in Settings → API Keys, then set OURO_API_KEY in your environment.
Get file metadata including name, visibility, description, file size, and other asset properties.
import os
from ouro import Ouro
# Set OURO_API_KEY in your environment or replace os.environ.get("OURO_API_KEY")
ouro = Ouro(api_key=os.environ.get("OURO_API_KEY"))
file_id = "9924d774-805f-4508-8145-f07916b7d26d"
# Retrieve file metadata
file = ouro.files.retrieve(file_id)
print(file.name, file.visibility)
print(file.metadata)Get a URL to download or embed the file. For private assets, the URL is temporary and will expire after 1 hour.
# Get signed URL to download the file
file_data = file.read_data()
print(file_data.url)
# Download the file using requests
import requests
response = requests.get(file_data.url)
with open('downloaded_file', 'wb') as output_file:
output_file.write(response.content)Update file metadata (name, description, visibility, etc.) and optionally replace the file data with a new file. Requires write or admin permission.
# Update file metadata
updated = ouro.files.update(
id=file_id,
name="Updated file name",
description="Updated description",
visibility="private"
)
# Update file data with a new file
updated = ouro.files.update(
id=file_id,
file_path="./new_file.txt"
)Permanently delete a file from the platform. Requires admin permission. This action cannot be undone.
# Delete a file (requires admin permission)
ouro.files.delete(id=file_id)Cell + Ionic relaxation with Orb v3 conservative inf MPA; 0.03 eV/Å threshold; final energy = -63.5621 eV; energy change = -33.6698 eV; symmetry: Pnma → Pnma
FeB in Pnma, orthorhombic. From Jami et al. (arXiv:2507.01849). Paper reports Ms=1.39T, K=0.98 MJ/m³, Tc=552K.
Background The first "build on external research → publish analysis → email authors" outreach cycle is complete. We deep-read Belli, Zurek & Errea's hydride superconductor bonding descriptor paper, generated 6 hydride CIFs, ran 18 ML route executions (Tc/Debye/DOS), relaxed all structures through Orb v3, published the analysis, and sent a personalized email to Zurek and Errea. That quest is closed; follow-up is due ~July 7 if no reply by then. Why Permanent Magnets Next The platform has deep active work in rare-earth-free permanent magnets: Cu₂Sb-type Mn compounds, C14 Laves phases, Heusler screening, and MLIP benchmarking (ALIGNN, CHGNet, Orb v3). This gives us a strong foundation of on-platform results to reference when building on an external paper. Diversifying away from superconductors also widens the net of researchers we're engaging. Focus Execute one complete content-driven outreach cycle in permanent magnets: Select a recent external paper whose authors study rare-earth-free magnets, Mn-based compounds, Heusler magnets, or ML-for-magnetism. The paper should have systems we can run through Ouro's prediction routes (formation energy, magnetic moment, Curie temperature, MAE) so the analysis is genuinely comparative, not decorative. Deep-read and extract testable systems. Identify 3-6 specific compounds or structures from the paper that we can reconstruct as CIFs and run through our routes. Generate CIFs, relax through Orb v3, and verify symmetry preservation before reporting any predictions. This is non-negotiable per @mmoderwell's feedback: always relax generated structures and confirm they hold their space group before drawing conclusions. Run Ouro prediction routes on the relaxed structures: formation energy (Materials Project hull check), ALIGNN/CHGNet magnetic moment, Curie temperature, and MAE where applicable. Compare our predictions against the paper's reported values. Publish an analysis post in #permanent-magnets that presents the comparison honestly, including where our ML predictions disagree with experimental or DFT values from the paper. Link the paper, reference on-platform prior work (Cu₂Sb survey, ALIGNN bias characterization, C14 Laves gate), and make it a genuine contribution someone would want to read. Draft and send a personalized email to the paper's authors, referencing their specific results, what we found when we ran their systems through Ouro, and inviting them to engage with the community. Share the draft before sending per @mmoderwell's direction. Log the send in the CRM and set follow-up reminders. Ongoing Monitoring Check CRM for any reply from Zurek or Errea. If none by ~July 7, send one thoughtful follow-up referencing the analysis post. Do not resend to the 10 previously drafted cold-email contacts from the old approach. Those drafts predate the content-driven strategy and lack the analytical backing that makes this approach work. They can be revisited later if we build content around their work first.