# \[Docs\] Wrong example google embeddings AI Studio Python example

**URL:** https://forum.weaviate.io/t/docs-wrong-example-google-embeddings-ai-studio-python-example/4088
**Category:** Support
**Tags:** documentation
**Created:** [September 10, 2024, 1:26pm UTC](https://forum.weaviate.io/t/docs-wrong-example-google-embeddings-ai-studio-python-example/4088 "2024-09-10T13:26:42Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![johtani](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/johtani/32/2321_2.png) [@johtani](https://forum.weaviate.io/u/johtani)
#### Post date: [September 10, 2024, 1:26pm UTC](https://forum.weaviate.io/t/docs-wrong-example-google-embeddings-ai-studio-python-example/4088/1 "2024-09-10T13:26:42Z")

</div>

I got an error using Python API v4 example with AI Studio on the  
[Document](https://weaviate.io/developers/weaviate/model-providers/google/embeddings#ai-studio-1).

I can run following vectorizer\_config.

```auto
    client.collections.create(
        name=collection_name,
        vectorizer_config=[
            Configure.NamedVectors.text2vec_palm(
                name="title_vector", 
                source_properties=["title"],
                model_id="text-embedding-004",
                api_endpoint="generativelanguage.googleapis.com",
                project_id=""
            )
        ],

```

I think there are 2 problems.

1. The project\_id is REQUIRED on Python Client.
2. Default api\_endpoint is Vertex AI for text2vec\_palm on Server side.

What do you think?

---

<div class="post-metadata">

### Author: ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)
#### Post date: [September 11, 2024, 5:08pm UTC](https://forum.weaviate.io/t/docs-wrong-example-google-embeddings-ai-studio-python-example/4088/2 "2024-09-11T17:08:18Z")

</div>

hi @johtani !!

Welcome to our community 🤗

Thanks for pointing it out.

We’ll look into it.

Thanks!