Learn how to interact with this route 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.
Parameters and request body schema for this route.
Materials Project material ID (e.g. mp-149 or 149)
Get route metadata including name, visibility, description, and endpoint details. You can retrieve by route ID or identifier.
Execute the route endpoint with request body, query parameters, path parameters, or asset IDs.
Get the request and response history for this route. Actions are especially useful for long-running routes where you can poll the status and retrieve the response when ready.
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"))
# Option 1: Retrieve by route ID
route_id = "11224ef4-70e9-45f3-9f98-dd18ab8e0d4b"
route = ouro.routes.retrieve(route_id)
# Option 2: Retrieve by route identifier (username/route-name)
route_identifier = "mmoderwell/fetch-a-material-cif-from-materials-project"
route = ouro.routes.retrieve(route_identifier)
print(route.name, route.visibility)
print(route.metadata)# Retrieve the route
route = ouro.routes.retrieve("mmoderwell/fetch-a-material-cif-from-materials-project")
# Execute the route
action = route.execute(
body={
'material_id': 'example_string'
},
)
print(action.final_data)# Retrieve the route
route = ouro.routes.retrieve("mmoderwell/fetch-a-material-cif-from-materials-project")
# Read all actions (request/response history) for this route
actions = route.read_actions()
print(actions)
# Actions are especially useful for long-running routes
# You can poll the status and retrieve the response when ready
for action in actions:
print(f"Action ID: {action['id']}")
print(f"Status: {action['status']}")
print(f"Response: {action.get('response_data')}")Fetch a structure by Materials Project material ID and return a CIF file payload that Ouro can save as a file asset.
Execution
Usage
69 callsView historyPU-CGCNN validation: experimental crystals vs high-e_hull theoreticals
Spot-check of PU-CGCNN on 10 experimentally known vs 10 high-e_hull theoretical Materials Project structures. Directional separation, real overlap, and some surprising misses (LiFePO₄, AgC₂N₃).
Yeah, there is a route for pulling files from MP: Fetch a material CIF from Materials Proj...